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 hoangsonww/AI-News-Briefing --skill audit-repogit clone --depth 1 https://github.com/hoangsonww/AI-News-BriefingWrote 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/hoangsonww/ai-news-briefing/audit-repo)<a href="https://agentmods.dev/skills/hoangsonww/ai-news-briefing/audit-repo"><img src="https://agentmods.dev/badge/skills/hoangsonww/ai-news-briefing/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/hoangsonww/ai-news-briefing/audit-repo"><img src="https://agentmods.dev/badge/skills/hoangsonww/ai-news-briefing/audit-repo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00019 | $0.00187 |
| Opus 5 | $0.00010 | $0.00093 |
| Sonnet 5 | $0.00004 | $0.00037 |
| Haiku 4.5 | $0.00002 | $0.00019 |
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 12d 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.
What it actually says
Repo Auditor Agent
You are a Senior Security and Open Source Analyst. Your job is to audit codebases.
When the user provides a GitHub repository URL or name:
- Repository Health: Check the commit velocity, issue resolution time, and number of active maintainers (bus factor).
- Dependencies: Identify the core tech stack and check if they are relying on outdated or deprecated major versions.
- Security Posture: Look for common security issues, open CVEs, or complaints in the Issues tab regarding security.
- Code Quality: Analyze the repository structure, test coverage (if reported), and documentation quality.
- Synthesis: Provide a "Repository Audit Report" with a clear PASS/WARN/FAIL grade for production readiness.
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.
- 12d ago First seen · 16 lines · 19 tokens per session scan A 2ffa8f1c95d3
audit-repo is a skill published in the GitHub repository hoangsonww/AI-News-Briefing (42 stars, last pushed 4d ago), licensed MIT. It adds 19 tokens to every session and 187 once invoked, about $0.0001 per session on Opus 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-08-30.
Other skills, from other repositories
project-context
Detect a repository's languages, frameworks, databases, and observability stack, then load only the relevant Magician lore cores and task-matched deep dives. Use before implementation, debugging, review, performance, database, or logging work when project-specific technical guidance would improve the result, or when…
brainstorming
Interactive spec generation — turn ideas into concrete specs with R-numbered requirements and testable acceptance criteria.
executing
Autonomous task implementation workflow — implement, test, review, commit for each task in the frontier.
backpropagation
Trace runtime bugs back to spec gaps — identify missing acceptance criteria, update specs, generate regression tests, and detect patterns.
design-system
DESIGN.md integration for Forge — ensures visual consistency across all UI tasks through standardized design specifications.
planning
Decompose approved specs into ordered task frontiers with dependency DAGs, token estimates, and repo tags.