mk:jira-admin — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited mk:jira-admin (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Forks to the jira-admin agent. Highest-blast-radius leaf in the family.
Admin role. Insufficient permission → exit code 3.
project delete — IRREVERSIBLEuser delete — IRREVERSIBLE (use deactivate instead when possible)group delete with members — affects member access globallyThe agent enforces 2-step token confirmation for these. The skill triggers them via natural language; the agent never auto-executes without explicit human-typed confirmation.
jira-as admin <sub-domain> --help for the authoritative flag list.../../agents/jira-admin.md../jira/references/{install-and-auth,cli-idioms,safety-framework}.mdreferences/voodoo-constants.md — magic numbers (event IDs, scheme IDs, common custom field IDs) and how to discover yoursmk:jira-fields (field admin overlap; fields create requires admin), mk:jira-jsm (JSM-specific admin lives in jira-jsm). Most users invoke mk:jira-admin once per project setup, then never again.~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.