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.
git 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/plugins/agenturehq/agenture-loop/agn)<a href="https://agentmods.dev/plugins/agenturehq/agenture-loop/agn"><img src="https://agentmods.dev/badge/plugins/agenturehq/agenture-loop/agn/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/plugins/agenturehq/agenture-loop/agn"><img src="https://agentmods.dev/badge/plugins/agenturehq/agenture-loop/agn.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
agn 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.
What it actually says
{
"name": "agn",
"description": "Agentic SDLC for Claude Code — Claude facilitates writing specs and designing architecture, then autonomously builds implementation plans, implements and tests the product. Driven by structured /agn:* skills with built-in review gates and document consistency.",
"version": "0.1.0",
"author": {
"name": "Vladimir Kroz"
},
"repository": "https://github.com/AgentureHQ/agenture-loop"
}
What it installs
The manifest is a name and a version. 9 skills, 2 agents travel with it, and installing the plugin installs all of them — 589 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 10 lines scan A 4dfbc3030bc6
agn is a plugin published in the GitHub repository AgentureHQ/agenture-loop (2 stars, last pushed 4mo ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
multi-cursor
Official Cursor SDK coding harness.
lid-experimental
Experimental LID skills with opt-in installation and explicit lifecycle (promotion or retirement). Layers on top of linked-intent-dev and arrow-maintenance.
the-blueprint
Structured planning pipeline implementing DRAFT: discovery, research, alignment, frame, tasks, plus work-item creation, YouTrack mechanics, glossary, living decision records, and technical diagramming.
open-source
Open-source contribution discipline: issue writing, pull request creation, and contribution etiquette.
rust
Rust language discipline: ownership, idioms, error handling, concurrency (threads/rayon and async), toolchain, testing, and LSP-powered code intelligence.
code-cleanup
Evidence-first cleanup of agent trajectory residue, dead islands, split-brain authority, stale dependencies, and unnecessary code across repositories.