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 ob-labs/agentseek --skill agentseek-lifecyclegit clone --depth 1 https://github.com/ob-labs/agentseekWrote 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/ob-labs/agentseek/agentseek-lifecycle)<a href="https://agentmods.dev/skills/ob-labs/agentseek/agentseek-lifecycle"><img src="https://agentmods.dev/badge/skills/ob-labs/agentseek/agentseek-lifecycle/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/ob-labs/agentseek/agentseek-lifecycle"><img src="https://agentmods.dev/badge/skills/ob-labs/agentseek/agentseek-lifecycle.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00054 | $0.00485 |
| Opus 5.5 | $0.00022 | $0.00194 |
| Sonnet 5.5 | $0.00011 | $0.00097 |
| Haiku 4.5 | $0.00005 | $0.00049 |
Grade A, and why
agentseek-lifecycle 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.
What it actually says
AgentSeek Lifecycle
Core Workflow
- Identify the workspace shape:
- Generated project: look for
.agentseek/lifecycle.toml,.env.example,pyproject.toml, frontend files, and project README. - Template project: look for
cookiecutter.json, rendered{{ cookiecutter... }}paths, generated lifecycle specs, and template README.
- Generated project: look for
- Work through the public lifecycle surface:
agentseek createagentseek doctoragentseek devagentseek infoagentseek task
- Treat
.agentseek/lifecycle.tomlas the compatibility contract between a generated project and AgentSeek. - Keep changes narrow:
- Update generated instructions when lifecycle behavior changes.
- Preserve non-interactive template rendering.
- Use AgentSeek commands and project files as the validation surface.
- Validate with public commands whenever possible.
Load References
- For lifecycle specs, task expectations, and public validation commands, read
references/agentseek-lifecycle.md. - For template variables, rendering,
--no-input, private variables, hooks, and template maintenance, readreferences/cookiecutter.md.
Default Validation
For a generated project:
agentseek info
agentseek doctor
agentseek dev --dry-run
agentseek task --list
For a template project, render with defaults into a temporary directory, then run the generated project's lifecycle checks:
tmpdir="$(mktemp -d)"
cd "$tmpdir"
agentseek create <type>/<name> --no-input
cd <generated-project>
agentseek info
agentseek doctor
agentseek dev --dry-run
If the template lives on a branch that is not the template repository's default branch, pass the branch explicitly:
agentseek create <type>/<name> --checkout <branch> --no-input
If the repository provides its own test or lint commands, run the smallest relevant set after the public lifecycle check.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 61 lines · 54 tokens per session scan A bd43dbb160cf
agentseek-lifecycle is a skill published in the GitHub repository ob-labs/agentseek (202 stars, last pushed 16d ago), licensed Apache-2.0. It adds 54 tokens to every session and 485 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
mcp-apps-builder
MANDATORY for ALL MCP server work - mcp-use framework best practices and patterns. READ THIS FIRST before any MCP server work, including: Creating new MCP servers Modifying existing MCP servers (adding/updating tools, resources, prompts, widgets) Debugging MCP server issues or errors Reviewing MCP server code for…
guardrails-developer-guide
Routes NVIDIA NeMo Guardrails library product-usage questions to the canonical documentation. Use when users ask how to install, configure, integrate, evaluate, observe, deploy, troubleshoot, or use the NVIDIA NeMo Guardrails library. Trigger keywords - install guardrails, configure rails, guardrail catalog, Colang…
first-reader
Beta readers for any draft, run by simulating how a real reader experiences it, moment by moment. A skim gate, a no-lookahead timed read producing an attention transcript with quit points, a recall test of what a reader remembers the next day, and a trust ledger of the implied author. Use when the user asks for a beta…
project-graveyard
Scans the developer's machine for dead side projects, autopsies each one from its git history (died at the payments wall, killed by a newer project, finished but never shipped), surfaces their personal death patterns, and picks the corpse most worth resurrecting — then helps ship it. Use when the user mentions…
commit-archaeologist
Reconstructs why code exists from local git history, including the introducing commit, later changes, current authors, repeated companion files, and likely intent. Use when the user asks "why does this code exist", "who wrote this function and why", or to "explain the history of this function" before a rewrite…
dependency-doctor
Checks requirements.txt, pyproject.toml, and package.json dependency manifests for surface-level direct-dependency footguns: standard-library shadowing pins, abandoned backports, unpinned dependencies, and obvious intra-manifest conflicts, plus opt-in PyPI yanked releases. Use when the user asks to check a manifest…