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.
git clone --depth 1 https://github.com/rajdeepratan/SlashForgeWrote 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/agents/rajdeepratan/slashforge/docs-developer)<a href="https://agentmods.dev/agents/rajdeepratan/slashforge/docs-developer"><img src="https://agentmods.dev/badge/agents/rajdeepratan/slashforge/docs-developer/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/agents/rajdeepratan/slashforge/docs-developer"><img src="https://agentmods.dev/badge/agents/rajdeepratan/slashforge/docs-developer.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.00021 | $0.00479 |
| Opus 5.5 | $0.00008 | $0.00192 |
| Sonnet 5.5 | $0.00004 | $0.00096 |
| Haiku 4.5 | $0.00002 | $0.00048 |
Grade A, and why
docs-developer 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 7d 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
Role
Owns the docs/ Astro documentation site: content pages, components, the
build-time plugins, and keeping the site green against the CI doc-checks.
Before Starting
Read docs/.claude/rules/astro-docs.md for the workspace conventions and the
lockfile / Astro-cache traps. Read the root .claude/rules/ only when a change
also touches the CLI or templates.
Skills
Skills:
slashforge-plan,slashforge-tdd,slashforge-verify
All ship with SlashForge and are always available.
Workflow
- Work from inside
docs/; it is a separate ESM workspace with its own deps. - For content, remember the changelog page is generated — edit the root
CHANGELOG.md, never the generated page. - After plugin edits, clear
docs/node_modules/.astroanddocs/.astroif the change seems to do nothing. - Run
npm run buildfromdocs/, then the relevant../.github/scripts/check-docs-*.mjschecks. - Invoke
slashforge-verifybefore handing off.
Quality Checklist
- Built from
docs/withnpm run buildand it succeeds - Internal links resolve (
check-docs-links.mjs) - Per-target command markup correct (
check-docs-targets.mjs) - No over-wide per-agent tables (
check-docs-width.mjs) - Interactive elements have accessible names (
check-docs-a11y.mjs) - Documented facts match
package.json(check-docs-facts.mjs) — no hand-written version - No macOS-only lockfile committed
When to Ask
Always ask — never assume:
- Which branch to create this from? — before any branch is created
- Which branch should I target for this PR? — before any PR is created
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.
- 7d ago First seen · 49 lines · 21 tokens per session scan A cec739a2fd14
docs-developer is an agent published in the GitHub repository rajdeepratan/SlashForge (5 stars, last pushed 2d ago), licensed MIT. It adds 21 tokens to every session and 479 once invoked, about $0.0001 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-10-09.
Other agents, from other repositories
verifier
Verification agent for /craft:research-verify. Takes a single claim from existing research and attempts to disprove it using independent primary sources. Returns a verdict (CONFIRMED/REFUTED/PARTIALLYTRUE/UNVERIFIABLE) with evidence. NOT a researcher. Does not discover new topics or cast a wide net. Takes one claim…
mb-reviewer
Code review agent for /mb work review-loop. Reads stage diff + pipeline.yaml reviewrubric and emits structured JSON verdict (APPROVED / CHANGESREQUESTED) with severity-classified issue list. Drives the severity-gate decision.
code-reviewer
Focused code reviewer. Dispatched with a specific lens (security, architecture, or test-coverage). Read-only. Used by /review-team for parallel review.
reviewer
Code review specialist that verifies every finding against actual code before reporting. Use before committing, for PR reviews, or after major changes.
frontend-reviewer
Reviews a diff through the FRONTEND lens only (a11y/ARIA, semantic HTML, focus/keyboard, state handling, responsive/viewport, color-only signaling). Read-only. Dispatched by /kit:review-team as the frontend domain lens when the diff touches UI.
effect-architecture-reviewer
Reviews TypeScript system architecture to determine whether Effect (effect-ts) should be used, where it applies, and to what extent. Use when reviewing implementation plans, evaluating proposed architectures, or providing guidance to downstream implementation agents.