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 thettwe/nyann --skill gen-claudemdgit clone --depth 1 https://github.com/thettwe/nyannWrote 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/thettwe/nyann/gen-claudemd)<a href="https://agentmods.dev/skills/thettwe/nyann/gen-claudemd"><img src="https://agentmods.dev/badge/skills/thettwe/nyann/gen-claudemd/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/thettwe/nyann/gen-claudemd"><img src="https://agentmods.dev/badge/skills/thettwe/nyann/gen-claudemd.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.00208 | $0.01017 |
| Opus 5 | $0.00104 | $0.00508 |
| Sonnet 5 | $0.00042 | $0.00203 |
| Haiku 4.5 | $0.00021 | $0.00102 |
Grade A, and why
gen-claudemd 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 9d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gen-claudemd
Standalone CLAUDE.md regeneration. Wraps bin/gen-claudemd.sh with the
same inputs bootstrap uses, but skips the full bootstrap pipeline so the
user can refresh CLAUDE.md after changing their profile, adding docs, or
restructuring workspaces.
1. Gather inputs
The generator needs three inputs. Resolve them in this order:
- Profile — resolve the active profile via preferences or CLAUDE.md
markers; load with
bin/load-profile.sh <name>. If the user names a specific profile, use that instead. - Doc plan — the generator needs a DocumentationPlan. To preserve
the repo's existing doc routing (local / Obsidian / Notion / split),
re-derive the plan using the same routing the user originally chose.
Check
profile.documentation.storage_strategy; if it names a non-local backend, also runbin/detect-mcp-docs.shand pass--mcp-targetsto route-docs. For local-only repos (the common case):bin/route-docs.sh --profile <profile-path>suffices. Write the resulting DocumentationPlan JSON to a temp file. - Stack (optional but recommended) — run
bin/detect-stack.sh --path .for a StackDescriptor JSON. Write it to a temp file. Skip if detection fails (gen-claudemd falls back to profile-only data).
For monorepos, also resolve workspace configs:
bin/resolve-workspace-configs.sh --stack <stack-path> --profile <profile-path>
Pass the result via --workspace-configs <path>.
2. Snapshot the current state
Before running the generator, capture the existing managed block so
you can show a before/after diff. If CLAUDE.md exists with markers,
read the content between <!-- nyann:start --> and
<!-- nyann:end -->. If no markers exist, note that a new block will
be appended.
3. Confirm before writing
Ask: "Regenerate the nyann-managed block in CLAUDE.md?"
Show what will feed into the generation (profile name, stack, storage strategy) so the user can verify the inputs are correct. Skip the confirmation only when the user said "just do it".
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.
- 9d ago First seen · 101 lines · 208 tokens per session scan A d1755c180472
gen-claudemd is a skill published in the GitHub repository thettwe/nyann (6 stars, last pushed 10d ago), licensed MIT. It adds 208 tokens to every session and 1,017 once invoked, about $0.0010 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-31.
Other skills, from other repositories
meta-tags-optimizer
Optimize title tags, meta descriptions, Open Graph, and Twitter cards for maximum click-through rate. Generates multiple A/B test variations with character counting and SERP preview. Use when asked to "optimize title tag", "write meta description", "improve CTR", "Open Graph tags", "fix my meta tags", "social media…
google-ads-audit
Google Ads account audit and business context setup. Run this first — it gathers business information, analyzes account health, and saves context that all other ads skills reuse. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should…
sxo
Search Experience Optimization (SXO) — the bridge between SEO and UX/CRO. Audits the full journey from the SERP click to the on-page goal: SERP click-through factors (title/meta/rich results that win the click), then post-click experience signals that keep users and drive conversions — above-the-fold relevance and…
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
security
Enforce Elixir/Phoenix security — auth, OAuth, sessions, CSRF, XSS, SQL injection, input validation, secrets. Use when editing auth files, login flows, RBAC, or API keys.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.