Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add narrative-io/narrative-skills-marketplace --skill audit-repogit clone --depth 1 https://github.com/narrative-io/narrative-skills-marketplaceWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/narrative-io/narrative-skills-marketplace/audit-repo)<a href="https://agentmods.dev/skills/narrative-io/narrative-skills-marketplace/audit-repo"><img src="https://agentmods.dev/badge/skills/narrative-io/narrative-skills-marketplace/audit-repo/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/narrative-io/narrative-skills-marketplace/audit-repo"><img src="https://agentmods.dev/badge/skills/narrative-io/narrative-skills-marketplace/audit-repo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00075 | $0.03423 |
| Opus 5.5 | $0.00030 | $0.01369 |
| Sonnet 5.5 | $0.00015 | $0.00685 |
| Haiku 4.5 | $0.00007 | $0.00342 |
Grade A, and why
audit-repo scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 14d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 284 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/audit-repo
Load the ledger, grade this week's rubric, file the failures worth filing, and report coverage — including what you could not check.
This skill is read-only. No edits, no commits, no branches, no pull requests. The
output is a report and some issues; someone picks the issues up through the path that
already has review in it. An auditor that also merges its own findings has no adversary.
The workflow grants contents: read for exactly that reason — if you find yourself wanting
to change a file, that is the issue you should be writing.
Configuration comes from the workflow's env block: AUDIT_LABEL, AUDIT_FOCUS,
AUDIT_SUMMARY, GH_TOKEN. Running this by hand, accept the defaults named below.
Step 1 — preflight
gh auth status
If that fails, stop and say so. Do not audit anyway. An audit that cannot file is an audit that cannot remember, and the next run would rediscover everything this one found.
Step 2 — read the ledger before you read any repository file
gh issue list --repo "$GITHUB_REPOSITORY" \
--label "${AUDIT_LABEL:-repo-audit}" --state all --limit 500 \
--json number,title,state,stateReason,labels,body,url \
> "${RUNNER_TEMP:-/tmp}/ledger.json"
Every issue ever filed under the label, in every state. Read all of it and sort each entry:
| Bucket | How to tell | What it means |
|---|---|---|
| Open | state is OPEN |
Filed and waiting. Never refile. |
| Fixed | state is CLOSED, stateReason is COMPLETED |
Shipped. Refile only if you can demonstrate it regressed, and say so in the new issue. |
| Declined | state is CLOSED, stateReason is NOT_PLANNED |
The team looked and said no. Permanent skip. |
Declined is permanent, and permanent means in any wording. Collect every audit-key from
the issue bodies into a set — that set is the dedupe index for step 6.
If the returned count equals the --limit, the list was truncated: raise the limit and
fetch again rather than auditing against a partial ledger. This step is graded by
AUD-RUN-01. Record the entry count and the distinct-key count.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 14d ago First seen · 284 lines · 75 tokens per session scan A 4a43e1c2180d
audit-repo is a skill published in the GitHub repository narrative-io/narrative-skills-marketplace (9 stars, last pushed today), licensed MIT. It adds 75 tokens to every session and 3,423 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-26.
Other skills, from other repositories
project-closeout
A final project check that reviews product documents, technical documents, task status, tracked issues, and system health before closing the work.
tech-debt
Track, categorize and prioritize technical debt across the codebase — scans for debt indicators, maintains a register.
pr-review-triage
Watch open PRs, check CI status, review staleness, merge conflicts, and unanswered review comments. Produces a prioritized watchlist.
maintain
Triage and work through Ouroboros GitHub issues and pull requests as a maintainer. Use for ooo maintain, backlog cleanup, review, merge readiness, duplicate PRs, and issue disposition.
spec-kitty-runtime-review
Review runtime-owned outputs using the Spec Kitty review workflow surface, then direct approval or rejection with structured feedback. Triggers: "review this work package", "check runtime output", "approve this step", "review WP", "is this WP ready to approve", "check this implementation". Does NOT handle: setup-only…
cocoplus-config
CocoPlus configuration SSOT — $cocoplus sync propagates cocoplus.toml into downstream artifacts; $cocoplus migrate-config converts legacy safety-config.json. Invoked via $cocoplus sync and $cocoplus migrate-config.