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/agenturehq/agenture-loop/definenpx skills add AgentureHQ/agenture-loop --skill definegit clone --depth 1 https://github.com/AgentureHQ/agenture-loopWhat 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.00064 | $0.05497 |
| Opus 5 | $0.00032 | $0.02749 |
| Sonnet 5 | $0.00013 | $0.01099 |
| Haiku 4.5 | $0.00006 | $0.00550 |
Grade A, and why
define 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 2d 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 — 498 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Define (/agn:define <level>)
Arguments
| Position | Variable | Value |
|---|---|---|
$0 |
level | product, epic, feature, or task |
$1+ |
hints | Optional title or, for task, kind (task | bug) |
Argument validation
If $0 is missing, stop and ask:
"What level — product, epic, feature, or task?"
If $0 is not one of product, epic, feature, task, stop and list the valid set.
Dispatch
Read $0. Run exactly one of the four workflows below.
Composition via the Planner sub-agent
For epic, feature, and task levels, composition of the unit body (and decomposition into child units, where applicable) is delegated to the Planner sub-agent (plugins/agn/agents/planner.md). This skill stays focused on user dialog, slug confirmation, and taskman.sh persistence.
The product branch does not invoke the Planner — vision/spec/requirements drafting is pre-Design and stays in the parent session. Product-level Design (architecture) lives in /agn:design product; the epic list comes from /agn:define epic calls afterward.
When a workflow below says "delegate to the Planner", invoke it via the Agent tool with subagent_type: planner and a brief containing:
level—epic|feature|taskmode—newtitle— the human-readable titleinitial_scope— what the user said in the dialog so far (problem, objective, scope, acceptance criteria, any decomposition discussed)upstream— paths to relevant docs (docs/vision.md,docs/spec.md,docs/requirements.md,docs/architecture.md; parent epic or feature file)
The Planner returns:
## Body— full markdown body for the unit, matching the required sections fromrules/task-composition.md.## Decomposition— ordered child list (empty fortask).- Optional
## Questions for parent— surface to the user, gather answers, re-invoke the Planner with the updated brief.
Pipe the returned Body to ./scripts/taskman.sh new <level> --slug … --title …. For each Decomposition entry, invoke ./scripts/taskman.sh new for that child after composing its own body (which may delegate to the Planner one more level down).
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.
- 2d ago First seen · 498 lines · 64 tokens per session scan A 32d9d32efa40
define is a skill published in the GitHub repository AgentureHQ/agenture-loop (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 64 tokens to every session and 5,497 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-31.
Other skills, from other repositories
issue-triage
Issue triage: audit open issues, categorize, detect duplicates, cross-ref PRs, risk assessment, post comments. Args: "all" for deep analysis of all, issue numbers to focus (e.g. "42 57"), "en"/"fr" for language, no arg = audit only in French.
coordinate
Coordinate a small team of Qwen Code teammates with enforced read-only workers, an optional worktree-pinned writer, shared tasks, peer messages, and existing Agent View tabs. Invoke explicitly with /coordinate.
gh-issues
Use when creating, triaging, or commenting on GitHub issues for the Kilo VS Code extension or JetBrains plugin via gh. Covers issue templates, project board assignment, title conventions, and required gh scopes.
batch-all-issues
Resolve every open issue one at a time: fact-check each with web research, close the ones that need no action, and run the goal-pr skill to fix, review, and merge the ones that do — repeating until no actionable issues remain.
resolve-scrap-issues
Fetch recent maintainer-scrap issues, validate each with web research, then either close the ones that need no action or open a single consolidated pull request that resolves the ones that do.
create-issue
Create a GitHub issue with detailed description, purpose, and appropriate labels.