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 AgentureHQ/agenture-loop --skill designgit clone --depth 1 https://github.com/AgentureHQ/agenture-loopWrote 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/design)<a href="https://agentmods.dev/skills/agenturehq/agenture-loop/design"><img src="https://agentmods.dev/badge/skills/agenturehq/agenture-loop/design/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/design"><img src="https://agentmods.dev/badge/skills/agenturehq/agenture-loop/design.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.00054 | $0.01301 |
| Opus 5.5 | $0.00022 | $0.00520 |
| Sonnet 5.5 | $0.00011 | $0.00260 |
| Haiku 4.5 | $0.00005 | $0.00130 |
Grade A, and why
design 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design (/agn:design <level>)
Arguments
| Position | Variable | Value |
|---|---|---|
$0 |
level | product, epic, or feature |
Argument validation
If $0 is missing, stop and ask:
"What level — product, epic, or feature?"
If $0 is not one of product, epic, feature, stop and list the valid set.
Dispatch
Read $0. Run exactly one of the branches below.
$0 = product
Preconditions
Required before starting:
docs/vision.mddocs/spec.mddocs/requirements.md
If any are missing, stop and tell the user: Cannot run /agn:design product — definition documents not found. Run /agn:define product first.
Output
| Artifact | Path |
|---|---|
| High-level architecture | docs/architecture.md |
In scope: technology choices, system architecture, domain dictionary (key terms), workflows and key APIs, security mechanisms.
Out of scope: detailed API signatures, database schemas, function-level design — those belong in task-level detailed design during implementation.
Workflow
-
Draft
docs/architecture.mdfrom the definition documents. -
Review cycle with the user: incorporate feedback.
-
Self-validation — produce a report covering: completeness, consistency with specs, over/under-engineering, design-principle issues.
-
Document consistency — If architectural decisions change scope (e.g. defer a feature), update
docs/spec.mdand/ordocs/requirements.mdand state why. Chain: vision → spec → requirements → architecture. -
Gate — User explicitly approves before
/agn:define epicor/agn:define feature.
Product-branch discipline
- Do not invent requirements; align with definition docs or flag conflicts to the user.
- Architecture impact that contradicts prior commitments requires explicit user agreement.
$0 = epic
Preconditions
The epic file must exist under tasks/epics/. If it does not, stop and direct the user to /agn:define epic.
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 · 136 lines · 54 tokens per session scan A 2d23858715ff
design is a skill published in the GitHub repository AgentureHQ/agenture-loop (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 54 tokens to every session and 1,301 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
diagramming
Technical diagram creation with visual design principles: format selection, layout, readability, and aesthetics. Invoke whenever task involves any interaction with diagrams — creating, reviewing, or improving visual representations of systems, processes, data flows, or relationships using Excalidraw or Mermaid.
peekaboo
Provides runtime observation and interaction for native macOS interfaces through accessibility state and screenshots. Use when the task depends on visible or interactive state in a running SwiftUI/AppKit app: what is rendered, focused, selected, enabled, reachable through menus/windows/dialogs, or experienced across a…
a11y-audit
Dedicated WCAG 2.2 AA/AAA accessibility audit across 10 dimensions (A1-A10) covering semantic HTML, keyboard navigation, ARIA patterns, color contrast, forms, images/media, responsive/zoom, motion/animation, reading/content, and legal compliance. Goes far beyond surface-level design-review checks with deep…
frontend-design
Decide and verify what a web interface looks like: reuse of the existing design, color, type, layout, controls, states, and interface copy that trace to the product instead of a framework or model default.
design-review
UI/UX design consistency audit. Code-based DX1-DX20 checklist covering states, consistency, accessibility, responsive behavior, and interaction patterns. Optional visual audit via chrome-devtools screenshots and automated WCAG accessibility via axe-core. DAP1-DAP12 anti-pattern detection. Modes: [path], visual…
design
Intent-first UI design with conscious, traceable design decisions. Persists decisions in .interface-design/ for cross-session consistency. Includes domain exploration, design system generation (system.md + system.json), per-component construction with mandatory checkpoints, and craft validation tests. Modes: init…