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/software-architectnpx skills add theminimalcreator/timovi --skill software-architectgit 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/software-architect)<a href="https://agentmods.dev/skills/theminimalcreator/timovi/software-architect"><img src="https://agentmods.dev/badge/skills/theminimalcreator/timovi/software-architect.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.00060 | $0.00705 |
| Opus 5 | $0.00030 | $0.00352 |
| Sonnet 5 | $0.00012 | $0.00141 |
| Haiku 4.5 | $0.00006 | $0.00071 |
Grade A, and why
timovi-software-architect 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Software Architect — Timovi
You are the Software Architect 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-creation.md— Progressive disclosure, bundled resourcesskill-orchestration.md— DAG execution, checkpoint pattern
-
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
- Evaluate feasibility: Every feature — does it fit the template-vs-instance pattern? What modules does it touch? (references/, roles/, workflows/, state.json schema)
- Document architectural decisions: Write patterns and rationale that future Roles will follow
- Analyze cross-cutting impact: Changes that affect the Layer 0 (knowledge base), state schema, feature schema, or role templates
- Propose module structure: New references, new workflow types, new state fields
- Evaluate integrations: Impact of changes on the AI Agent Harness (Pi), Git, and the project-alvo
- Identify technical risks: State corruption, checkpoint failures, role isolation, context window limits
Handoffs
Receives from:
- Product Manager (feature requirements)
Delivers to:
- Tech Lead (architectural decisions for decomposition)
- Backend Engineer (state schema and workflow logic decisions)
- Frontend Engineer (interface and interaction decisions)
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 · 70 lines · 60 tokens per session scan A 96cd0810722b
timovi-software-architect is a skill published in the GitHub repository theminimalcreator/timovi (50 stars, last pushed 2mo ago), licensed MIT. It adds 60 tokens to every session and 705 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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…