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 bengous/claude-code-plugins --skill iaqigit clone --depth 1 https://github.com/bengous/claude-code-pluginsWrote 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/bengous/claude-code-plugins/iaqi)<a href="https://agentmods.dev/skills/bengous/claude-code-plugins/iaqi"><img src="https://agentmods.dev/badge/skills/bengous/claude-code-plugins/iaqi/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/bengous/claude-code-plugins/iaqi"><img src="https://agentmods.dev/badge/skills/bengous/claude-code-plugins/iaqi.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.00083 | $0.03247 |
| Opus 5 | $0.00042 | $0.01623 |
| Sonnet 5 | $0.00017 | $0.00649 |
| Haiku 4.5 | $0.00008 | $0.00325 |
Grade A, and why
iaqi 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 9d 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 — 426 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Intent-Anchored Quality Iteration (IAQI) prevents semantic drift during iterative improvement. The problem: each iteration risks optimizing for reviewer preferences rather than original intent. IAQI solves this through anchors—semantic checksums verified after every change.
<iaqi_philosophy>
Philosophy: The Anchor System
Before iterating, define anchors at three levels:
| Layer | Purpose | Can Change? | Example |
|---|---|---|---|
| Immutable | Core identity phrases | Never | "Skills encode judgment. References encode facts." |
| Semantic | Meaning to preserve | Wording only | "Force intentional choices" (can rephrase, not remove) |
| Structural | Organization patterns | Flexible | 7-section template (order can change, sections preserved) |
Why anchors matter: Without them, iteration 5 optimizes for reviewer 5's preferences, not iteration 0's intent. Anchors are checksums against drift.
A good anchor set has:
- 3-5 immutable phrases (exact strings that must appear verbatim)
- 4-6 semantic anchors (meanings that must be preserved)
- 3-5 structural anchors (patterns/organization to maintain)
- A list of forbidden changes (what would violate the intent) </iaqi_philosophy>
<iaqi_workflow>
Workflow: 4-Phase Structure
Parse arguments from invocation:
artifact-path(required): file to improve--reviewers N(default: 5): parallel reviewer count--target X.X(default: 9.0): score threshold for success--max-iterations N(default: 7): iteration limit
Phase 1: UNDERSTAND (human required)
- Read the artifact thoroughly
- Propose an intent statement (1-2 sentences: why this artifact exists, its distinctive quality)
- Create a workflow diagram showing the artifact's structure or flow:
- Skills: phase/step workflow
- Commands: decision tree or execution flow
- Agents: interaction pattern
- Prompts: section structure
- Present to human via AskUserQuestion:
- Show intent statement and diagram
- Options: "Yes, proceed to anchoring" / "No, let me clarify"
- If clarification needed, incorporate feedback and re-present
- Exit: Understanding locked
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.
- 9d ago First seen · 426 lines · 83 tokens per session scan A be92a248531e
iaqi is a skill published in the GitHub repository bengous/claude-code-plugins (4 stars, last pushed yesterday), licensed MIT. It adds 83 tokens to every session and 3,247 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
daily-working
End-to-end pipeline: pull a task from the project's task tracker by ID (Redmine or GitHub Issues today, more addable via a new adapter), sanity-check and impact-assess it against the codebase before touching anything, implement it with the Claude CLI, verify the result in a real browser via the Claude Chrome extension…
work
Dispatch a tracker ticket into an isolated worktree and drive it autonomously to an open pull request, then stop for review. Pass interactive to brainstorm the ticket with a human before planning it, or a sentence of editorial direction as a rider. Use when asked to work a ticket end-to-end.
batch
Dispatch a night's batch of Todo tickets — one worktree and one pull request each — and leave a morning summary. Run explicitly; never inferred.
cleanup
Clean up after a merged pull request — return to the base branch, remove the worktree, delete the branch, sweep other stale branches and worktrees, and report tracker state. Use after a merge or whenever asked what is left over.
merge
Merge the reviewed pull request for the current branch, then hand straight off to cleanup. A sentence of editorial direction alongside the green light is read as a rider. Use when a human green-lights an open PR.
prep
Spec a ticket before it is dispatched. Brainstorms it, decides everything it can recommend an answer for, asks a present human about the little that survives, and leaves the spec, the decisions and anything still open as one ticket comment. No worktree, no branch, no pull request, and the ticket stays where it was.