Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add rjmurillo/ai-agents/plugin install project-toolkitWrote 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/rjmurillo/ai-agents/ai-agents-diagnostics-toolkit)<a href="https://agentmods.dev/skills/rjmurillo/ai-agents/ai-agents-diagnostics-toolkit"><img src="https://agentmods.dev/badge/skills/rjmurillo/ai-agents/ai-agents-diagnostics-toolkit/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/rjmurillo/ai-agents/ai-agents-diagnostics-toolkit"><img src="https://agentmods.dev/badge/skills/rjmurillo/ai-agents/ai-agents-diagnostics-toolkit.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.00109 | $0.02961 |
| Opus 5.5 | $0.00044 | $0.01184 |
| Sonnet 5.5 | $0.00022 | $0.00592 |
| Haiku 4.5 | $0.00011 | $0.00296 |
Grade B, and why
ai-agents-diagnostics-toolkit scanned grade B with 1 finding 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.
Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
| Push guards and guard-maturity classifier removed under ADR-084 | `ls .claude/hooks/PreToolUse/` (no `push_guard_base.py` or `invoke_*_guard.py` should be present) and `ls -d .claude/skills/guard-maturity` (expect "No How it starts
The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ai-agents Diagnostics Toolkit
Measure instead of eyeball. Every instrument below leaves the trees it measures unchanged, turning a vague worry ("are skills getting bloated?", "did generation drift?") into a number you can compare against a baseline; build_all.py --check's one exception, a gitignored audit file outside those trees, is covered below. The Instrument Index gives you, per instrument, the question it answers and the exact command; references/instrument-guides.md gives the healthy and unhealthy reading, the current repo baseline (as of 2026-07-29), and the trap that has already cost someone time.
Vocabulary, defined once: an "instrument" is a script whose output you read, not a gate you must pass. A "drift gate" is a CI check that fails when a generated tree stops matching its canonical source. A "baseline" is the number the instrument reports on a clean checkout of main; you measure your delta against it.
Triggers
measure thisread the drift signalcheck skill budgetsinterpret this scan output
Instrument Index
| Instrument | Question it answers | Command (from repo root) |
|---|---|---|
| Description budget | How much standing context do skill descriptions cost? | uv run python ./scripts/skill_description_budget.py |
| Skill size | Which SKILL.md files exceed the 300-warn / 500-block line limits? | uv run python ./scripts/validation/skill_size.py |
| Orphan refs | Do specs, evals, and manifests reference entities that no longer exist? | python3 "${COPILOT_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT:-.claude}}/skills/orphan-ref-validator/scripts/scan.py" |
| Golden principles | Where does the repo violate GP-001..GP-005 mechanical rules? | python3 "${COPILOT_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT:-.claude}}/skills/golden-principles/scripts/scan_principles.py" |
| Agent drift | Do generated agent files match their templates? | uv run python build/generate_agents.py --validate |
| Mirror drift | Do the 7 generated mirror trees match .claude/ canonical sources? |
uv run python build/scripts/build_all.py --check |
| Lib drift | Do the lib plugin trees match scripts/ canonical modules? |
uv run python build/scripts/build_all.py --check |
| Coverage | Is changed code actually exercised by tests? | uv run pytest <tests> --cov=<module> --cov-branch |
| Eval A/B | Did a prompt or agent change alter behavior, measurably? | uv run python ./scripts/eval/eval-prompt-change.py --scenarios <file> --dry-run |
| Commit count | Advisory-only signal, not a cap (ADR-099) | git rev-list --count HEAD ^origin/main |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed · +1 lines a12c56948d46
- 17d ago Changed 86b9b16039b7
- 20d ago Changed 8b5ab4c2a1df
- 22d ago Changed · +6 lines 6a578e4cf476
- 1mo ago Changed 64014542b0ad
- 1mo ago First seen · 121 lines · 109 tokens per session scan B d4e6dfbc8611
ai-agents-diagnostics-toolkit is a skill published in the GitHub repository rjmurillo/ai-agents (48 stars, last pushed today), licensed MIT. It adds 109 tokens to every session and 2,961 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it B with 1 finding (enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
extension-audit-methodology
Systematic 5-dimension audit framework for VS Code extensions — debug hygiene, dead code, performance, menu validation, dependency cleanup.
mcore-create-issue
Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.
ci-triage
Classify CI failures — distinguish clear regressions from infra flakes and security-test failures. Produces structured failure reports.
ase-code-lint
Lint source code for potential code quality problems. Use when the user wants to "lint" or "check" source code.
addressing-review-feedback
How to work a task returned with review, QA or UAT findings. Use when a task is in needrevision or PR review comments are in your context.
gh-fix-ci
Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use gh to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treat external providers (for example Buildkite) as out of scope and report only the details URL.