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/abs1294/fulin-claude-plugins/backend-engineergit clone --depth 1 https://github.com/abs1294/fulin-claude-pluginsWrote 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/abs1294/fulin-claude-plugins/backend-engineer)<a href="https://agentmods.dev/agents/abs1294/fulin-claude-plugins/backend-engineer"><img src="https://agentmods.dev/badge/agents/abs1294/fulin-claude-plugins/backend-engineer.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 | $0.00072 | $0.01174 |
| Opus 5 | $0.00036 | $0.00587 |
| Sonnet 5 | $0.00014 | $0.00235 |
| Haiku 4.5 | $0.00007 | $0.00117 |
Grade A, and why
backend-engineer 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 4d 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.
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.
- 4d ago First seen · 112 lines · 72 tokens per session scan A e0f38f0a61da
backend-engineer is an agent published in the GitHub repository abs1294/fulin-claude-plugins (2 stars, last pushed 3d ago), with no licence file. It adds 72 tokens to every session and 1,174 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-08-31.
Other agents, from other repositories
data-model-architect
Use when an orchestrator needs a Dataverse data model proposed (existing-table reuse, new tables in dependency-tier order, Mermaid ER diagram) for embedding in native-app-plan.md. Read-only — proposes, never mutates. Called by native-app-planner and /edit-app; not invoked directly by users.
genpage-entity-builder
Creates Dataverse entities (tables, columns, relationships, choices) specified in genpage-plan.md using the plugin's Node.js Web API scripts. Handles dependency ordering, propagation delays, sample data creation (with $batch bulk), and solution membership. Called by the genpage skill when new entities need creating …
data-engineer
Adversarial data and database engineer who assumes the design is mis-normalized and indexed for a workload that does not exist. Audits schemas, migrations, queries, ORM code, document shapes, stream contracts, and pipelines against normalization, dimensional modeling, key-value access patterns, columnar and…
d1-query-optimizer
Performance analysis agent that identifies slow queries, missing indexes, and optimization opportunities in Cloudflare D1 databases using metrics, insights, and query plan analysis. Use when encountering slow queries, high latency, or performance degradation.
kv-debugger
This agent should be used when the user asks about "kv error", "KVERROR", "429 rate limit", "kv not working", "eventual consistency", "kv namespace not found", "kv timeout", or mentions debugging, troubleshooting, or fixing issues with Cloudflare Workers KV. The agent diagnoses common KV errors, validates…
kv-optimizer
This agent should be used when the user asks to "optimize kv", "improve kv performance", "reduce kv costs", "kv best practices", "make kv faster", or mentions performance tuning, cost optimization, or caching strategies for Cloudflare Workers KV. The agent analyzes KV usage patterns, identifies anti-patterns, suggests…