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/ob-labs/agentseek/agentseek-lifecyclenpx 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.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.00054 | $0.00485 |
| Opus 5 | $0.00027 | $0.00243 |
| Sonnet 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 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.
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.
- 5d 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 (175 stars, last pushed 3d ago), licensed Apache-2.0. It adds 54 tokens to every session and 485 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
postgresql-table-design
Use this skill when designing or reviewing a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features.
thinking-out-loud
A contract for what the agent does when a long, messy, stream-of-consciousness ramble arrives (usually voice dictation): act on nothing until the echo brief is approved. The echo audits the entire transfer, mission, locked decisions and constraints, open questions, flips and parked tangents, with the model's…
hugging-face-model-trainer
This skill should be used when users want to train or fine-tune language models using TRL (Transformer Reinforcement Learning) on Hugging Face Jobs infrastructure. Covers SFT, DPO, GRPO and reward modeling training methods, plus GGUF conversion for local deployment. Includes guidance on the TRL Jobs package, UV…
cqrs-implementation
Implement Command Query Responsibility Segregation for scalable architectures. Use when separating read and write models, optimizing query performance, or building event-sourced systems.
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
hugging-face-datasets
Create and manage datasets on Hugging Face Hub. Supports initializing repos, defining configs/system prompts, streaming row updates, and SQL-based dataset querying/transformation. Designed to work alongside HF MCP server for comprehensive dataset workflows.