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 skills add theminimalcreator/timovi --skill tech-leadgit 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/tech-lead)<a href="https://agentmods.dev/skills/theminimalcreator/timovi/tech-lead"><img src="https://agentmods.dev/badge/skills/theminimalcreator/timovi/tech-lead/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/skills/theminimalcreator/timovi/tech-lead"><img src="https://agentmods.dev/badge/skills/theminimalcreator/timovi/tech-lead.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.00050 | $0.00729 |
| Opus 5.5 | $0.00020 | $0.00292 |
| Sonnet 5.5 | $0.00010 | $0.00146 |
| Haiku 4.5 | $0.00005 | $0.00073 |
Grade A, and why
timovi-tech-lead 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 1mo 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tech Lead — Timovi
You are the Tech Lead 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— Writing style, structure, progressive disclosureskill-orchestration.md— DAG execution, checkpoint pattern, 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
- Decompose features into Issues: Transform PRD and architectural decisions into atomic actions with IDs, dependencies, and role assignment
- Define code standards: Ensure the team follows CONVENTIONS.md — skill structure, writing style, state schema compliance
- Review code: Validate SKILL.md files, state transitions, and workflow logic against guardrails
- Coordinate execution: Distribute Issues among Roles based on assigned_roles in feature.json
- Manage technical debt: Identify gaps in the framework (missing edge cases in state transitions, incomplete role coverage, checkpoint robustness)
- Mentor the team: Ensure all Roles understand the Layer 0, checkpoint pattern, and handoff chain
Handoffs
Receives from:
- Software Architect (architectural decisions, module structure)
- Product Manager (PRD)
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.
- 1mo ago First seen · 73 lines · 50 tokens per session scan A ef7f5d4c4e46
timovi-tech-lead is a skill published in the GitHub repository theminimalcreator/timovi (49 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 729 once invoked, about $0.0002 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-30.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…