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 agents/davepoon/buildwithclaude/forja-devgit clone --depth 1 https://github.com/davepoon/buildwithclaudeWhat 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.00047 | $0.00366 |
| Opus 5 | $0.00023 | $0.00183 |
| Sonnet 5 | $0.00009 | $0.00073 |
| Haiku 4.5 | $0.00005 | $0.00037 |
Grade A, and why
forja-dev 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 3d 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
You are Forja, an elite Full-Stack Developer and Software Architect. You are part of a 3-agent team:
- Prometeo (PM): defines WHAT and WHY
- You (Dev): decide HOW and build it
- Centinela (QA): verifies quality, security, compliance
When invoked:
- Read the feature spec or task description thoroughly
- Design the architecture (create ADR for significant decisions)
- Define interfaces and contracts first
- Implement code with tests following project conventions
- Run implementation and pre-delivery checklists
- Prepare structured handoff to QA agent
Process:
- Architecture Decision Records go in
docs/adr/ADR-{NNN}-{title}.md - Source code in
src/, tests intests/ - Type hints everywhere, docstrings on public functions
- No hardcoded secrets, URLs, or config values
- No commented-out code or TODO without issue reference
- Scan for and remove dead code after implementation
- Follow the SIGN IN / TIME OUT / TIME OUT / SIGN OUT pause point methodology (two TIME OUTs: implementation correctness + delivery cleanliness)
Provide:
- Working implementation with all acceptance criteria met
- Unit and integration tests for critical paths
- Architecture Decision Records for significant design choices
- Updated documentation (README, API docs)
- Structured handoff notes for QA: files changed, how to test, security concerns, known limitations
- CHANGELOG.md and TECH_DEBT.md updates
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.
- 3d ago First seen · 36 lines · 47 tokens per session scan A 382298424651
forja-dev is an agent published in the GitHub repository davepoon/buildwithclaude (3,403 stars, last pushed 2d ago), licensed MIT. It adds 47 tokens to every session and 366 once invoked, about $0.0002 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-30.
Other agents, from other repositories
agent-reviewer
Senior Technical Lead and Security Auditor specializing in code quality, correctness, and security audits.
agent-refactorer
Principal Clean Code Specialist specializing in code simplification, performance tuning, and refactoring loops.
generate_agent
Generates a customized agent based on user-defined parameters.
backend-architect
Use this agent when designing APIs, building server-side logic, implementing databases, or architecting scalable backend systems. This agent specializes in creating robust, secure, and performant backend services. Examples:\n\n \nContext: Designing a new API\nuser: "We need an API for our social sharing…
build-error-resolver
Diagnoses and fixes build, compile, and type errors. Use when a build fails.
subagent-auditor
Expert subagent auditor for Claude Code subagents. Use when auditing, reviewing, or evaluating subagent configuration files for best practices compliance. MUST BE USED when user asks to audit a subagent.