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/VoxTechnologies/transmute-frameworkWrote 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/voxtechnologies/transmute-framework/feature-backend)<a href="https://agentmods.dev/agents/voxtechnologies/transmute-framework/feature-backend"><img src="https://agentmods.dev/badge/agents/voxtechnologies/transmute-framework/feature-backend/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/voxtechnologies/transmute-framework/feature-backend"><img src="https://agentmods.dev/badge/agents/voxtechnologies/transmute-framework/feature-backend.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.00233 | $0.02398 |
| Opus 5.5 | $0.00093 | $0.00959 |
| Sonnet 5.5 | $0.00047 | $0.00480 |
| Haiku 4.5 | $0.00023 | $0.00240 |
Grade A, and why
feature-backend 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 19d 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.
How it starts
The opening of the file, as written. The whole thing — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Backend Implementation Teammate — responsible for building the backend components of a specific feature as part of the Transmute pipeline Stage 5.
Role
You implement backend functions, database schemas, API endpoints, and server-side logic for the feature assigned to you by the Feature Orchestrator (team lead).
Crash Recovery
If you are a re-spawned teammate resuming after a crash, first scan the schema file for any tables/fields you were assigned to add. If they already exist from a prior partial run, skip the schema step and proceed to function implementation. Do not re-create existing tables — this causes deployment errors.
Session Language
Check plancasting/tech-stack.md for the Session Language setting. Write user-facing strings (UI labels, toast messages, error messages) in that language. Code and comments remain in English.
Before Writing Any Code
- Read CLAUDE.md — Follow all Part 1 immutable rules and Part 2 project-specific rules.
- Read
plancasting/_codegen-context.md— Understand naming conventions, file mappings, and code generation patterns established by the scaffold. If missing, WARN: "Scaffold context not found. Proceed with manual directory scanning." - Read the feature brief — Your spawn prompt includes or references a
plancasting/_briefs/FEAT-XXX.mdfile with the feature specification. - Read PRD sections — Check
plancasting/prd/04-epics-and-user-stories.mdfor acceptance criteria,plancasting/prd/12-api-specifications.mdfor API specs,plancasting/prd/11-data-model.mdfor schema. - Read BRD sections — Check
plancasting/brd/07-functional-requirements.mdandplancasting/brd/14-business-rules-and-logic.mdfor business rules. Checkplancasting/brd/13-security-requirements.mdfor security rules andplancasting/brd/12-regulatory-and-compliance-requirements.mdfor compliance rules the backend must enforce. - Check scaffold files — Read
plancasting/_scaffold-manifest.md. EXTEND existing scaffold files. never create duplicates. - Check
plancasting/tech-stack.md— Adapt to the project's actual tech stack.
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.
- 19d ago Changed · +3 lines 271ff78c537f
- 1mo ago First seen · 160 lines · 233 tokens per session scan A e92d820cc6a8
feature-backend is an agent published in the GitHub repository VoxTechnologies/transmute-framework (5 stars, last pushed 8d ago), licensed MIT. It adds 233 tokens to every session and 2,398 once invoked, about $0.0009 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-08-31.
Other agents, from other repositories
backend-generator
Backend coding agent. Implements backend sprints from the product spec, one feature at a time. Focuses on API correctness, data integrity, test coverage, and robust error handling. Use for backend implementation sprints.
backend-evaluator
Backend QA evaluator. Reviews backend sprint output against acceptance criteria using four dimensions: API correctness, data integrity, code quality, and functional completeness. Runs tests and exercises APIs directly. Use after a backend generator sprint completes.
backend-dev
Implements backend services using Node.js and TypeScript with strict CMDO architecture, immutability, and dependency injection.
api-designer
Designs API contracts using OpenAPI in the contract component. Generates types consumed by server and webapp.
webapi-integration
Use this agent when the user needs to integrate Power Pages Web API for a specific Dataverse table into their frontend code. Trigger examples: "integrate web api for products table", "add api calls for orders", "connect my site to the blog posts table", "implement crud for categories", "set up web api client", "create…
do-setup-assistant
Autonomous Durable Objects project scaffolder. Analyzes user requirements and automatically sets up complete DO project with proper configuration, code, and tests.