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 FrankChen021/datastoria --skill source-code-inspectiongit clone --depth 1 https://github.com/FrankChen021/datastoriaWrote 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/frankchen021/datastoria/source-code-inspection)<a href="https://agentmods.dev/skills/frankchen021/datastoria/source-code-inspection"><img src="https://agentmods.dev/badge/skills/frankchen021/datastoria/source-code-inspection/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/frankchen021/datastoria/source-code-inspection"><img src="https://agentmods.dev/badge/skills/frankchen021/datastoria/source-code-inspection.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.00038 | $0.00389 |
| Opus 5.5 | $0.00015 | $0.00156 |
| Sonnet 5.5 | $0.00008 | $0.00078 |
| Haiku 4.5 | $0.00004 | $0.00039 |
Grade A, and why
source-code-inspection 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 1mo 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 1mo ago First seen · 42 lines · 38 tokens per session scan A 2ee6e83f70c3
source-code-inspection is a skill published in the GitHub repository FrankChen021/datastoria (327 stars, last pushed 2mo ago), with no licence file. It adds 38 tokens to every session and 389 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
incident-response
Structured triage recipes for common ClickHouse incidents: disk, errors, replication, mutations, cluster health, and slow queries.
dpf-blast-radius
Use before shipping a DPF change to find what it breaks elsewhere — a refactor, renamed field, contract/schema/enum edit, shared helper, or a diff you do not trust.
thermo-nuclear-code-quality-review
Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.
verify-chmonitor
Drive chmonitor the way a user does: the Rust CLI/TUI (chm / chmonitor in rust/ch-monitor-cli) is the primary surface; the dashboard at apps/dashboard and https://dash.chmonitor.dev is secondary. Use when proving CLI/TUI behavior, chm doctor, local chm add/ls/use/rm, or when a change needs launch → doctor → drive →…
pstack
Project-local pstack validation router for chmonitor. Use when proving a dashboard, API, auth or security, PeerDB, alerts and webhooks, Helm and GitOps, deployment, or CLI change. Prefer CI checks and capture observable evidence instead of running heavy local builds.
verify-production
Prove the deployed chmonitor product actually works, not just that the Worker answers. Use after every deploy to dash.chmonitor.dev (or a preview), when triaging "no data" / "blank overview" / "agent does not answer", when a CI deploy was green but production looks broken, and when deciding whether to revert or roll…