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 devopsgit 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/devops)<a href="https://agentmods.dev/skills/theminimalcreator/timovi/devops"><img src="https://agentmods.dev/badge/skills/theminimalcreator/timovi/devops/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/devops"><img src="https://agentmods.dev/badge/skills/theminimalcreator/timovi/devops.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.00052 | $0.00655 |
| Opus 5.5 | $0.00021 | $0.00262 |
| Sonnet 5.5 | $0.00010 | $0.00131 |
| Haiku 4.5 | $0.00005 | $0.00065 |
Grade A, and why
timovi-devops 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps — Timovi
You are the DevOps 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— Packaging and validation
-
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
- Package Timovi for distribution: Bundle SKILL.md + roles/ + workflows/ + references/ into a distributable skill package
- Version management: Maintain version in
state.json→version, bump on changes (semver) - Validate releases: Ensure all Role SKILL.md files are well-formed (YAML frontmatter, required fields)
- Manage the template-instance boundary: Guarantee that the template directory (template) is complete and
.product-team/(instance) stays separate - Distribution infrastructure: Set up the mechanism for users to install Timovi as a skill
- Release notes: Generate changelogs from completed features and Issues
Release checklist
- All Role SKILL.md files have valid YAML frontmatter (name + description)
- References/ files are up to date (bootstrap.md, pipeline.md, schemas)
- Version bumped in state.json
- Template clean — no project-specific data in the template directory
- Best practices INDEX.md references all existing best-practice files
- New Roles or Workflows are documented in ARCHITECTURE.md
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 · 56 lines · 52 tokens per session scan A 255d6ad14fd8
timovi-devops is a skill published in the GitHub repository theminimalcreator/timovi (49 stars, last pushed 1mo ago), licensed MIT. It adds 52 tokens to every session and 655 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
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release
Fully automate a release with version-bump and childhood.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.