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 wrg32786/aigent-os --skill skill-auditgit clone --depth 1 https://github.com/wrg32786/aigent-osWrote 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/wrg32786/aigent-os/skill-audit)<a href="https://agentmods.dev/skills/wrg32786/aigent-os/skill-audit"><img src="https://agentmods.dev/badge/skills/wrg32786/aigent-os/skill-audit.svg" alt="Measured on agentmods" 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.00053 | $0.00881 |
| Opus 5 | $0.00026 | $0.00441 |
| Sonnet 5 | $0.00011 | $0.00176 |
| Haiku 4.5 | $0.00005 | $0.00088 |
Grade A, and why
Skill Audit 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 6d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Audit
Auditing the skill catalog itself. As the install grows from 5 skills to 50, the catalog goes from "I remember every skill" to "I have no idea what's in here." This skill makes the catalog legible to its owner.
When to use
- Once a quarter — hygiene pass
- When Caddy starts surfacing the wrong skill repeatedly (signals a trigger-pattern mismatch)
- When a new feature feels like it should be a skill but you can't remember if you already built one
- After importing a skill bundle from another principal (e.g., from a public aigent-OS release)
- When considering retiring a project area and want to know which skills go with it
What it produces
A markdown report with four sections:
Section 1 — All skills, sorted by last invocation
| Skill | Last used | Total invocations (90d) | Description |
|---|---|---|---|
| /open | today | 47 | Start session, load vault context |
| /close | today | 47 | End session, commit memory |
| /caddy-enroll | 5 days ago | 12 | Add a skill to Caddy index |
| /skill-name | 23 days ago | 3 | Example skill entry |
| /old-experiment | 89 days ago | 1 | DEAD — flagged for retirement |
Section 2 — Dead skills (last used >60 days, <3 total invocations)
These are candidates for retirement. List with:
- Skill name + path
- Last-used date
- Total invocations
- Recommendation: keep / archive / delete
Section 3 — Caddy mismatch detection
For each skill, compare the trigger keywords in .claude/skill-index.json against the actual prompt patterns that preceded each invocation. Flag mismatches:
⚠️ /channel-audit
Triggers: "channel status", "YPP progress", "kill a channel"
Actual prompts that led to invocation: "how are channels doing", "performance check", "review channels"
Suggested triggers to ADD: "performance check", "review channels", "how are channels doing"
Section 4 — Capability gaps
Heuristic: scan recent prompts (last 30 days) where Caddy fired no hint and the principal manually invoked Read/Bash/Grep instead of a skill. Cluster by keywords. If a cluster has 3+ instances, flag as a capability gap.
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.
- 6d ago First seen · 83 lines · 53 tokens per session scan A b9d39327c258
Skill Audit is a skill published in the GitHub repository wrg32786/aigent-os (18 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 881 once invoked, about $0.0003 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-09-01.
Other skills, from other repositories
hive.note-taking
Maintain a free-form scratchpad of decisions, extracted values, and open questions so context pruning doesn't lose anything you still need.
article
Write a publication-ready article in one of three angles - a trending long-form piece, a watched-repo thesis, or a project-through-a-lens essay. Optional Replicate hero image with --visual.
fork-fleet
Fork divergence monitor - tracks where the fleet's active forks diverge in CODE (unique commits, new/modified skills) and CONFIG (enable/var/model/schedule vs upstream), gated on real change.
fleet-control
Operate managed Aeon instances from memory/instances.json - health-check, dispatch, and status snapshots (control), plus a fleet scorecard of runs, tokens, cost, and reliability (scorecard).
github-trending
Curated trending across GitHub repos and the Hugging Face Hub (models, datasets, spaces) - filtered, clustered, and labeled by momentum with a one-line why-notable per pick.
token-pick
One token recommendation and one prediction market pick - scored, quantified, with a skip branch when signals are weak.