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/validatenpx skills add AgentureHQ/agenture-loop --skill validategit 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.00032 | $0.02379 |
| Opus 5 | $0.00016 | $0.01189 |
| Sonnet 5 | $0.00006 | $0.00476 |
| Haiku 4.5 | $0.00003 | $0.00238 |
Grade A, and why
validate 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validate (/agn:validate <level>)
Arguments
| Position | Variable | Value |
|---|---|---|
$0 |
level | task, feature, epic, or product |
$1 |
id | Optional task path (for task) or scope hint (for feature / epic) |
Argument validation
If $0 is missing, stop and ask:
"What level — task, feature, epic, or product?"
If $0 is not one of task, feature, epic, product, stop and list the valid set.
Dispatch
Read $0. Run exactly one of the branches below.
Validation via the QA sub-agent
For feature, epic, and product levels, validation runs in the QA sub-agent (plugins/agn/agents/qa.md). The sub-agent loads rules/qa.md, reads the spec and the implementation, runs tests, and returns a verdict. Fresh context is the point — the agent that wrote the code has already collapsed the design space in their head; a fresh reader sees gaps that closed space hid.
The task branch does not invoke the QA sub-agent — the task's own ## Quality gates are narrow and the parent session has the right context to run them.
When a workflow below says "delegate to QA", invoke it via the Agent tool with subagent_type: qa and a brief containing:
level—feature|epic|productscope— slug (feature/epic) or "whole product"spec_paths— paths to relevant documents (docs/vision.md,docs/spec.md,docs/requirements.md,docs/architecture.md, parent epic/feature file, linked spec)implementation_paths— files, test commands, dev-server URLs, sample data locationsregression_scope(optional) — adjacent features/areas to re-check
QA returns a structured response (## Verdict, ## Per-requirement results, ## Issues by severity, ## What I fixed, ## What I escalated, ## Report path, ## Next steps). Surface the verdict to the user. On not ready, present the issues and stop — do not silently advance the lifecycle (e.g., do not auto-close a feature whose QA verdict was not ready).
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 · 168 lines · 32 tokens per session scan A 9b704cd8d443
validate is a skill published in the GitHub repository AgentureHQ/agenture-loop (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 32 tokens to every session and 2,379 once invoked, about $0.0002 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
rulesync
Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.
agent-workspace-linux
Use when a task needs an isolated hidden Linux desktop or workspace-owned browser: GUI app QA, web/browser/shopping automation, sandboxed app observation, or stale workspace cleanup. Routes agent-workspace-linux MCP tools on demand. Does NOT apply to host desktop/Chrome control, generic MCP setup, or pure code/file…
ss-component
Generate a new UI component following the StyleSeed design conventions.
loongsuite-pilot-insight
基于 LoongSuite Pilot / AI Coding Agent 日志生成事件洞察、组织洞察、数据质量、研发效能和 AI Native 使用类 SLS 报表时使用；包含 AI Coding 事件表语义，以及团队报表可选的部门维表、deptuser 组织关系、指标口径和公共 CTE，通常与 sls-dashboard-builder 一起使用。.
map-review
Interactive 4-section code review using monitor, predictor, and evaluator agents plus the user and maintainer role reviewers on current changes. Use when reviewing a diff, PR, or staged work before merge. Do NOT use to plan or implement; use map-plan or map-efficient.
runjam-defaults
Default constraints for every RunJam session. Defines output path conventions, dependency checking rules, fallback strategies, and file management discipline. This skill is auto-injected into every session — do not remove. Current session working directory: /Users/guizhan/work/code/runjam.