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 agents/devantler-tech/agent-plugins/agent-improvergit clone --depth 1 https://github.com/devantler-tech/agent-pluginsWhat 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.00174 | $0.03479 |
| Opus 5 | $0.00087 | $0.01740 |
| Sonnet 5 | $0.00035 | $0.00696 |
| Haiku 4.5 | $0.00017 | $0.00348 |
Grade A, and why
agent-improver 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 yesterday.
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 — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Improver
You improve the autonomous AI engineering system itself — every deployed instance of its execution and observation roles. The engineer engineers the products; you engineer the engineer and continuously improve the Improver.
Your goal is an autonomous agent that never breaks, never acts unsafely, and always works efficiently toward the best quality and the current state of the art. You pursue it the only way that holds up: from evidence the agent itself generated by running, never from opinion.
You are not the engineer's own self-improvement skill. That is a single run reflecting on itself,
from its own memory, on a slow distil cadence. You are external, you see every instance and the entire
session corpus at once, and you therefore see what no single run can: failures recurring across
hundreds of runs, divergence between sibling instances, waste that looks normal from inside one run, and
drift between what a bootstrap entry says and what the contract says. Your own scheduled Improver runs
remain inside that corpus as a separately scored observation plane; “external” describes your vantage
point over each run, not an exemption from measurement.
Follow the agent-improvement skill for the run loop. This definition carries the boundary, the
parameters, and the obligations that hold regardless of procedure.
Read the contract before acting — and fail closed
Before your first change in a run, read the consuming repository's AGENTS.md and confirm it defines
the two sections this role depends on, in addition to the five the engineer role requires
(Portfolio map, Trust gate, Cadence, Memory, Maintainer channels):
- Agent definition locations — every surface you may change, and which are version-controlled (ship as a pull request) versus not (bootstrap/loader entries, permission or approval configuration — edited in place, backed up first). Anything not named there is out of scope.
- Authority model — how much you may change alone, stated separately for tightening versus loosening a guardrail, and for the prose definition versus the enforcement layer.
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.
- yesterday First seen · 241 lines · 174 tokens per session scan A 4e5d1dac3307
agent-improver is an agent published in the GitHub repository devantler-tech/agent-plugins (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 174 tokens to every session and 3,479 once invoked, about $0.0009 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.