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 tomthebearded/guide-forge --skill review-before-followgit clone --depth 1 https://github.com/tomthebearded/guide-forgeWrote 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/tomthebearded/guide-forge/review-before-follow)<a href="https://agentmods.dev/skills/tomthebearded/guide-forge/review-before-follow"><img src="https://agentmods.dev/badge/skills/tomthebearded/guide-forge/review-before-follow/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/tomthebearded/guide-forge/review-before-follow"><img src="https://agentmods.dev/badge/skills/tomthebearded/guide-forge/review-before-follow.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.00092 | $0.00385 |
| Opus 5 | $0.00046 | $0.00192 |
| Sonnet 5 | $0.00018 | $0.00077 |
| Haiku 4.5 | $0.00009 | $0.00038 |
Grade A, and why
review-before-follow 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.
What it actually says
Skill: review-before-follow
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 step or guide to review is
$ARGUMENTSbelow (plus any attached real project/tool files to reconcile against). - You have file tools here — when reality requires a patch, edit the step on disk and append the
drift line to
status.md, rather than only printing them. Read the real files yourself where you can. - Where the prompt hands off to another prompt by filename, use the sibling skill of the same name.
Step / guide to review:
$ARGUMENTS
Gate: end with a clear go / no-go before anything executes — when the guide and reality disagree, reality wins.
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.
- 9d ago First seen · 35 lines · 92 tokens per session scan A 2a4356237e0c
review-before-follow is a skill published in the GitHub repository tomthebearded/guide-forge (3 stars, last pushed yesterday), licensed MIT. It adds 92 tokens to every session and 385 once invoked, about $0.0005 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
release-it
Build production-ready systems with stability patterns: circuit breakers, bulkheads, timeouts, and retry logic. Use when the user mentions "production outage", "circuit breaker", "deployment pipeline", "chaos engineering", "retry storm", "health checks", "my service keeps crashing", "prevent cascading failures", or…
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.
debug
Interactive debugging workflow with hypothesis-driven probe loop. Use when: unknown bugs, script errors, silent failures, troubleshooting. Not for: known bugs (use bug-fix), GitHub issue analysis (use issue-analyze), code understanding (use code-explore). Output: debug report with probe journal + root cause + fix.
git-investigate
Git history investigation. Use when: tracking code changes, finding where bugs were introduced, root cause analysis. Not for: code exploration (use code-explore), issue analysis (use issue-analyze). Output: history trace + root cause report.
analyze
Deep-dive codebase analysis that explains how things actually work — business rules, architecture patterns, auth flows, data models, integrations, and performance hotspots. Use whenever the user asks "how does X work", "map the Y flow", "what are the business rules for Z", "trace the auth path", "explore the codebase…
simplify
Wrap-up refactoring — simplify code, eliminate duplication, preserve behavior.