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/bromso/metapowersWrote 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/bromso/metapowers/development)<a href="https://agentmods.dev/plugins/bromso/metapowers/development"><img src="https://agentmods.dev/badge/plugins/bromso/metapowers/development/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/bromso/metapowers/development"><img src="https://agentmods.dev/badge/plugins/bromso/metapowers/development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
development 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 today.
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
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "development",
"version": "0.3.0",
"description": "Process-oriented software development workflow: plan, build, test, debug, review, and ship",
"author": {
"name": "Jonas Broms"
},
"repository": "https://github.com/bromso/metapowers",
"homepage": "https://bromso.github.io/metapowers/",
"license": "MIT",
"keywords": ["development", "tdd", "debugging", "code-review", "planning", "workflow"]
}
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.
- today First seen · 14 lines scan A bcc1e402c254
development is a plugin published in the GitHub repository bromso/metapowers (2 stars, last pushed today), licensed MIT. 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-10-21.
Other plugins, from other repositories
technology
Architecture, engineering delivery, development discipline, debugging, review, and AI and automation systems.
han-coding
Coding-facing skills for the Han suite: writing, reviewing, testing, investigating, and standardizing code. Home of the tdd skill, which drives a feature or behavior through a BDD-framed red-green-refactor loop with an enforced observed-failure gate, and the refactor skill, which restructures existing code without…
fuse-changelog
Claude Code update watcher: changelog tracking, breaking changes detection, community pulse via Exa, plugin compatibility analysis.
fuse-ai-pilot
AI Pilot workflow agents: sniper (code quality), research-expert, explore-codebase, websearch.
rust-intel
Defense against LLM Rust failure modes: 59 categories of bugs that survive rustc, clippy, and cargo test — async cancellation, unsafe/FFI, concurrency, crypto, supply-chain, tests-that-pass-by-luck, semantic conformance, and systemic performance cost. Ships the rust-intel skill plus /rust-intel:audit, /rust-intel:fix.
craftsman
Ship something with Lovable, Replit, Bolt, v0, Claude Code, or Codex and it works, but nobody with an engineering background has checked it. This is the engineering review you'd get from the technical co-founder you don't have. craft-audit checks the whole project across ten areas: UX, frontend, backend, database…