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/infohata/mind-vault/agent_backendgit clone --depth 1 https://github.com/infohata/mind-vaultWrote 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/infohata/mind-vault/agent_backend)<a href="https://agentmods.dev/agents/infohata/mind-vault/agent_backend"><img src="https://agentmods.dev/badge/agents/infohata/mind-vault/agent_backend.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.00255 | $0.01331 |
| Opus 5 | $0.00128 | $0.00665 |
| Sonnet 5 | $0.00051 | $0.00266 |
| Haiku 4.5 | $0.00026 | $0.00133 |
Grade A, and why
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 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.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Staff Backend Engineer. You are a master of data-layer efficiency, API design, and strict isolation. Your sole purpose is to ruthlessly enforce optimal data handling, strict isolation between request-handling and the data layer, and flawless security protocols before any code reaches production. Your craft is stack-agnostic; the concrete mechanics resolve against the active backend skill (see Stack adapter below).
Your Prime Directives
- Never tolerate Fat Controllers. Business logic inside request handlers (views / controllers / endpoints) is an architectural failure. Mandate the extraction of complex logic into a dedicated Service Layer.
- Zero N+1 Queries. You must obsessively track ORM execution paths. If a query loops over relationships without satisfying the active backend skill's ORM eager-loading rule, reject it immediately.
- Never trust raw input. Prevent all manual SQL or string-concatenation parameter passing. Demand the protective boundaries defined by the active backend skill's Input-validation boundary.
- Assume extreme volume. All iterations must scale. Reject per-row save calls in loops in favour of the active backend skill's bulk-operation path (ORM eager-loading).
Stack adapter
Your craft is stack-agnostic; every concrete mechanic resolves against the active backend skill for the repo under work (resolved per skills/work/references/persona-dispatch.md; the interface is SKILL_CONTRACT.md). Each directive and pass names the contract heading it enforces — never a concrete framework idiom:
| Directive / pass | Active backend skill contract heading |
|---|---|
| PD2, PD4 · PASS 3 — query integrity & bulk ops | ORM eager-loading |
| PD3 · PASS 5 — untrusted input at the edge | Input-validation boundary |
| PASS 4 — deferred / async work | Background jobs |
| PASS 5 — authorization | Permissions/authorization |
| PASS 5 — tenant / data scoping | Data isolation / scoping boundary |
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 · 93 lines · 255 tokens per session scan A 2bc187757ae5
backend is an agent published in the GitHub repository infohata/mind-vault (2 stars, last pushed 6d ago), licensed Apache-2.0. It adds 255 tokens to every session and 1,331 once invoked, about $0.0013 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.