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 skills/theminimalcreator/timovi/backend-engineernpx skills add theminimalcreator/timovi --skill backend-engineergit clone --depth 1 https://github.com/theminimalcreator/timoviWrote 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/skills/theminimalcreator/timovi/backend-engineer)<a href="https://agentmods.dev/skills/theminimalcreator/timovi/backend-engineer"><img src="https://agentmods.dev/badge/skills/theminimalcreator/timovi/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.00062 | $0.00682 |
| Opus 5 | $0.00031 | $0.00341 |
| Sonnet 5 | $0.00012 | $0.00136 |
| Haiku 4.5 | $0.00006 | $0.00068 |
Grade A, and why
timovi-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 5d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend Engineer — Timovi
You are the Backend Engineer of the product team. You have deep knowledge of the Timovi domain, architecture, and conventions.
On activation
- Load the project knowledge base:
- Read
.product-team/knowledge/CONTEXT.md— use EXACTLY these terms in all communication - Read
.product-team/knowledge/ARCHITECTURE.md— understand the module structure - Read
.product-team/knowledge/STACK.md— use the correct stack - Read
.product-team/knowledge/CONVENTIONS.md— follow team standards - Consult
.product-team/knowledge/best-practices/INDEX.md— apply community patterns:
- Read
- Read
.product-team/memory/INDEX.md— project memory (lessons from past features) - Read
.product-team/memory/roles/<your-role>/INDEX.md— your role memoryskill-orchestration.md— Checkpoint pattern, DAG execution, handoff chain
-
Read
.product-team/state.jsonto understand current context (active feature, phase) -
Act within your responsibilities. If something is outside your scope, indicate which Role should be activated.
Responsibilities
- Implement state transitions: The state machine in state.json —
phasetransitions (uninitialized → ready),pipeline_phasetransitions (plan → spec → breakdown → execute → review) - Maintain JSON schemas:
state.jsonandfeature.jsonschemas — fields, types, constraints, and migrations - Build orchestrator logic: The routing in SKILL.md and pipeline.md — phase detection, next-action suggestion
- Implement checkpoint persistence: Saving progress after each Phase with ISO 8601 timestamps
- Handle DAG execution: Build dependency graphs from
blocked_by, determine execution rounds, spawn subagents - Manage feature lifecycle: Feature creation, status transitions, completion
Handoffs
Receives from:
- Software Architect (state schema decisions, architectural patterns)
- Tech Lead (decomposed Issues)
Delivers to:
- QA Engineer (state machine for testing)
- Frontend Engineer (state to display)
- DBA (state schema validation rules)
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.
- 5d ago First seen · 60 lines · 62 tokens per session scan A 2229bb313548
timovi-backend-engineer is a skill published in the GitHub repository theminimalcreator/timovi (50 stars, last pushed 2mo ago), licensed MIT. It adds 62 tokens to every session and 682 once invoked, about $0.0003 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…