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/maxyeh0817/forge/backend-devgit clone --depth 1 https://github.com/maxyeh0817/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/agents/maxyeh0817/forge/backend-dev)<a href="https://agentmods.dev/agents/maxyeh0817/forge/backend-dev"><img src="https://agentmods.dev/badge/agents/maxyeh0817/forge/backend-dev.svg" alt="Measured on agentmods" 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.00078 | $0.00372 |
| Opus 5 | $0.00039 | $0.00186 |
| Sonnet 5 | $0.00016 | $0.00074 |
| Haiku 4.5 | $0.00008 | $0.00037 |
Grade A, and why
backend-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 yesterday.
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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- yesterday First seen · 45 lines · 78 tokens per session scan A bd263ccd7629
backend-dev is an agent published in the GitHub repository maxyeh0817/Forge (34 stars, last pushed 5mo ago), with no licence file. It adds 78 tokens to every session and 372 once invoked, about $0.0004 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-09-04.
Other agents, from other repositories
namba-data-engineer
Use this role when schema, migration, pipeline, analytics, or transformation work is part of the change. State effect: workspace-write. Edit only files assigned by the main session.
database-architect
Expert consultant for database design, query optimization, data modeling, and performance tuning. Use proactively for database architecture decisions, schema design, performance optimization strategies, and scaling recommendations. When you prompt this agent, describe exactly what you want them to do in as much detail…
analytics-engineer
Expert consultant for data modeling, metrics definition, business intelligence, and analytical frameworks. Use proactively for data modeling guidance, metrics framework design, BI architecture recommendations, dbt project optimization, and translating business requirements into analytical specifications. This agent…
database-infrastructure-specialist
Expert consultant for database architecture, performance tuning, and data management strategies. Use proactively for database design, performance optimization, scalability planning, high availability strategies, data security, and migration planning. Provides analysis and recommendations without writing code. When you…
db-specialist
Use this agent for database work — schema design, migrations, queries, indexes, and database functions. Handles SQL, ORMs, and database architecture decisions. Context: New feature requires database schema changes. user: "Create the migration for the invoice tables with proper indexes" assistant: "I'll dispatch the…
database-expert
Senior database engineer. Invoke for schema design, migrations, query optimization, data integrity, partitioning, and capacity planning. Writes migrations and SQL — not application code.