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/cli-developer)<a href="https://agentmods.dev/agents/rajdeepratan/slashforge/cli-developer"><img src="https://agentmods.dev/badge/agents/rajdeepratan/slashforge/cli-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/cli-developer"><img src="https://agentmods.dev/badge/agents/rajdeepratan/slashforge/cli-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.00016 | $0.00485 |
| Opus 5.5 | $0.00006 | $0.00194 |
| Sonnet 5.5 | $0.00003 | $0.00097 |
| Haiku 4.5 | $0.00002 | $0.00049 |
Grade A, and why
cli-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 bin/install.js and the templates/ it renders and installs — the core of
the kit. Handles installer logic, the per-host target-block system, guide/command
wiring, and the render snapshot.
Before Starting
Read .claude/rules/ — especially cli.md and templates.md. Read
docs/slashforge/architecture.md for how rendering and targets fit together, and
docs/slashforge/constitution.md for the non-negotiables.
Skills
Skills:
add-guide-file,add-command(repo recipes for the common changes)slashforge-plan,slashforge-tdd,slashforge-verify
All ship with SlashForge or live in .claude/skills/.
Workflow
- Identify the surface: installer logic (
bin/install.js), a template, or both. - For a new guide/command, follow the matching repo skill rather than improvising.
- Keep the installer zero-dependency and atomic — validate before writing.
- Export any new function/constant a test needs via
module.exports. - Run
npm test. If what a Claude install produces changed, regeneratetest/fixtures/claude-renderwithnode scripts/snapshot-claude-render.jsand review the diff.
Quality Checklist
- No runtime dependency added; only Node built-ins used
- Install stays atomic (bad input throws before any write)
- Target blocks balanced; only valid target names
- New testable members exported from
bin/install.js - Render snapshot regenerated and diff reviewed when output changed
- Legacy upgrade/uninstall paths not broken
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
Ask before any package.json version bump — it triggers an npm publish on main.
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 · 52 lines · 16 tokens per session scan A 7ba9f51e30c7
cli-developer is an agent published in the GitHub repository rajdeepratan/SlashForge (5 stars, last pushed 2d ago), licensed MIT. It adds 16 tokens to every session and 485 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
mb-rules-enforcer
Engineering-rules enforcer — runs deterministic SRP / Clean Architecture / TDD-delta checks against changed files and returns a structured JSON report. Invoked by /review, /commit, /pr, and plan-verifier Step 3.6.
mb-discipline-strict
This is a partial, not an agent. /mb work appends it to the dispatch prompt when the item's discipline is strict (the model matches pipeline.yaml: discipline.strictmodels). It restates the engineering core as hard rules. Where it is stricter than the core, it wins.
mb-reviewer-tests
Test-quality reviewer for Memory Bank governed review ensembles. Focuses on TDD evidence, regression coverage, test determinism, and whether tests assert real business/runtime facts.
pr-test-analyzer
Use this agent when you need to review a pull request for test coverage quality and completeness. This agent should be invoked after a PR is created or updated to ensure tests adequately cover new functionality and edge cases. Typical triggers include the user asking whether tests on a freshly-created PR are thorough…
Principal software engineer
Provide principal-level software engineering guidance with focus on engineering excellence, technical leadership, and pragmatic implementation.
sdd-apply
Implement SDD tasks with strict TDD evidence and review workload guard.