Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/AgentureHQ/agenture-loopnpx agentmods add skills/agenturehq/agenture-loop/implementWrote 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/agenturehq/agenture-loop/implement)<a href="https://agentmods.dev/skills/agenturehq/agenture-loop/implement"><img src="https://agentmods.dev/badge/skills/agenturehq/agenture-loop/implement/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/agenturehq/agenture-loop/implement"><img src="https://agentmods.dev/badge/skills/agenturehq/agenture-loop/implement.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.00041 | $0.03011 |
| Opus 5.5 | $0.00016 | $0.01204 |
| Sonnet 5.5 | $0.00008 | $0.00602 |
| Haiku 4.5 | $0.00004 | $0.00301 |
Grade A, and why
implement 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 2mo 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 — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement (/agn:implement <level> <id>)
Arguments
| Position | Variable | Value |
|---|---|---|
$0 |
level | task, feature, or epic |
$1 |
id | Task file path (for task) or slug (for feature / epic) |
Argument validation
If $0 is missing, stop and ask:
"What level — task, feature, or epic?"
If $0 is not one of task, feature, epic, stop and list the valid set.
If $1 is missing, stop and ask the user for the task path or slug.
Lifecycle actions — always via taskman.sh
All file moves and status transitions go through scripts/taskman.sh. Do not mv task files or edit YAML status by hand.
./scripts/taskman.sh move <task-path> active # backlog → active
./scripts/taskman.sh move <task-path> done # active → done
./scripts/taskman.sh feature close <slug> # close feature when all tasks done
./scripts/taskman.sh epic close <slug> # close epic when all features done
Design gap escalation protocol
When /agn:implement task detects a meaningful design gap during detailed design (missing scope detail, ambiguous acceptance criterion, undefined interface contract), it halts, writes a gap-log entry, and routes the user to the upstream skill that should address it. This protocol preserves the Design/Implementation separation: implementers do not silently improvise design.
Gap-log file format
Gap-log files live at tasks/gaps/<YYYYMMDD-HHMMSS>_<task-slug>.md. One file per detected gap. Written via the Write tool directly — not through taskman.sh (gaps are observability records, not lifecycle units).
Frontmatter:
---
detected: 2026-05-26T15:23:00Z # ISO 8601 with timezone
task: <task-slug>
task_path: tasks/active/YYYYMMDD_<slug>.md
suspected_level: task | feature | epic | architecture
status: open | resolved
---
Body sections (all required):
# Gap: <one-line description>
## Description
<what design information is missing or ambiguous>
## Detection context
<which step of /agn:implement task surfaced this; what the implementer was trying to do at the moment of detection>
## Suspected upstream
<which level needs revision; which skill the user should invoke>
## Resolution
<filled when the gap is marked resolved; left empty initially>
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.
- 2mo ago First seen · 287 lines · 41 tokens per session scan A ee2da9ddfc1d
implement is a skill published in the GitHub repository AgentureHQ/agenture-loop (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 41 tokens to every session and 3,011 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-31.
Other skills, from other repositories
youtrack
Work YouTrack as an agent: what a project configures rather than fixes, what a write changes besides the field it names, and which failures report success. Not what a work item should say.
task-creation
Write and review work items in an issue tracker: establish which reader the item is for, verify every claim it makes against the system, and give the implementer a location and acceptance criteria. Sizing and decomposition belong to tasks.
tasks
Work item decomposition — break implementation phases into sized, dependency-mapped tasks, each producing a verifiable artifact. Invoke whenever task involves the T stage of the DRAFT pipeline, decomposing phases into tasks, or creating a task breakdown.
handoff
Triage this conversation into a standalone transfer document — decisions, constraints, resource identifiers, verification state, and remaining work — for a session restart or a teammate.
backlog
Manage the project's tech debt backlog. Add, list, fix, wontfix, delete, prioritize, and suggest batch actions on tracked issues, run by the user to manage accumulated debt (skills file their findings through /.zuvo/backlog-add themselves, never through this skill). Modes: list [category], add [description], fix B- …
retro
Engineering retrospective from git metrics. Reports deployment frequency, release cycle span, churn hotspots, backlog health. Outputs narrative report with 3+ actionable items. Flags: --since, --path, explicit range argument.