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 agentmods add skills/tomthebearded/guide-forge/amend-guidenpx skills add tomthebearded/guide-forge --skill amend-guidegit clone --depth 1 https://github.com/tomthebearded/guide-forgeWhat 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 | $0.00170 | $0.00720 |
| Opus 5 | $0.00085 | $0.00360 |
| Sonnet 5 | $0.00034 | $0.00144 |
| Haiku 4.5 | $0.00017 | $0.00072 |
Grade A, and why
amend-guide 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 2d 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
Skill: amend-guide
The complete, canonical contract for this skill is the paste-prompt it wraps, inlined here — follow it in full:
!cat "${CLAUDE_SKILL_DIR}/prompt.md"
(If the block above came back empty or errored, read prompt.md in this skill folder — it sits beside this SKILL.md — and follow that.)
As you follow it, adapt for the fact that you're a Claude Code skill, not a pasted prompt:
- You're already invoked — skip its "How to use / paste this" preamble. The change request is
$ARGUMENTSbelow (plus any attached files). Read the guide'sguide/files yourself:progress.mdandstatus.mdfirst, thenPLAN.mdand the milestone folders the change reaches. - You have file tools here — write the amended files to disk rather than only printing fenced blocks.
Create
foundation/progress.mdfromtemplates/progress.mdif it's missing. - The gate is real, and it is the point. Deliver the impact report and stop. Write nothing until the user approves — not the "obvious" edits, not the foundation docs, not a placeholder. Step 0's progress gate is the same: if the frontier is unknown or contradicted, stop and ask before anything else.
- Executed steps are read-only except for the superseded banner. Never renumber, rename, move or delete a
file that
progress.mdmarks executed. - You have web access — verify every version, API and config key the change introduces against the official docs. Never assert one from memory.
- Hand off to the sibling skills, not the prompt files:
/mark-progressto record what's been executed (or to clear an[!]row once the reader applies a correction),/report-issuefor a defect you noticed on the way past,/audit-guideon the milestones you touched.
Change request / args:
$ARGUMENTS
Gate: no frontier, no amendment — and no writes before the impact report is approved. Rewrite only ahead of
the frontier, banner-only behind it, the repair in the first unexecuted step, amended milestones ⏳ and never
✅. Leave all changes in the working tree — do not commit.
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.
- 2d ago First seen · 50 lines · 170 tokens per session scan A cc53619ac853
amend-guide is a skill published in the GitHub repository tomthebearded/guide-forge (3 stars, last pushed 12d ago), licensed MIT. It adds 170 tokens to every session and 720 once invoked, about $0.0009 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
shadow-tutor
Post-session programming tutor for a developer who wants to grow. Use after an AI-assisted coding session to learn from it — it picks the one load-bearing decision the AI made that you most likely don't truly understand, makes you predict why before it reveals (breaking the "I get it" illusion), teaches the why…
codetrain
Use when the user wants to be taught/walked through code one tiny step at a time — triggers like "teach me this code", "walk me through this", "hold my hand", "explain step by step", "tutor me", "guide me through", "I want to learn this", or asks for a safe practice exercise to learn a concept.
learning-tutor
Use when a developer wants to learn about the codebase, start a learning session, understand how something works, or progress through the curriculum. Activates when the intent is learning rather than doing. Trigger phrases: "I'm new here", "walk me through", "help me understand", "start a learning session", "what…
curriculum-reviewer
Use when reviewing AI-generated curriculum content in the human review queue. Activates when working through .codebase-mooc/memory/humanreviewqueue.jsonl or when asked to review, approve, or assess generated curriculum content. Trigger phrases: "review the curriculum", "check the review queue", "approve this content"…
trulens-notebook-execution
Execute and display Jupyter notebooks for TruLens demos and quickstarts.
eli5
Explain research, papers, or technical ideas in plain English with minimal jargon, concrete analogies, and clear takeaways. Use when the user says "ELI5 this", asks for a simple explanation of a paper or research result, wants jargon removed, or asks what something technically dense actually means.