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/23ag1/completelyWrote 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/23ag1/completely/plugin)<a href="https://agentmods.dev/plugins/23ag1/completely/plugin"><img src="https://agentmods.dev/badge/plugins/23ag1/completely/plugin/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/23ag1/completely/plugin"><img src="https://agentmods.dev/badge/plugins/23ag1/completely/plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
completely 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 1mo 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": "completely",
"version": "0.11.0",
"description": "Quality-first harness for autonomous AI coding agents: deterministic gates + a default-FAIL evaluator in the close path of the loop, over a Beads task spine. Done is earned, not asserted. Unifies GSD + Beads; stack-agnostic.",
"author": {
"name": "23ag1",
"email": "[email protected]"
},
"homepage": "https://github.com/23ag1/completely",
"keywords": ["claude-code", "claude-code-plugin", "ai-coding-agent", "autonomous-coding", "ai-agent-harness", "agent-harness", "quality-gates", "default-fail-evaluator", "agent-evaluation", "agentic-coding", "beads", "gsd", "tdd", "developer-tools"]
}
What it installs
The manifest is a name and a version. 8 skills, 1 agent, 3 hooks travel with it, and installing the plugin installs all of them — 710 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill completely:plan A 96 tokens
- Skill completely:auto A 88 tokens
- Skill completely A 64 tokens
- Skill completely:control A 92 tokens
- Skill completely:run A 79 tokens
- Skill completely:sync A 73 tokens
- Skill completely:check A 81 tokens
- Skill completely:init C 75 tokens
- Agent evaluator A 62 tokens
- Hook PostToolUse A not measured
- Hook Setup A not measured
- Hook PreToolUse A not measured
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.
- 1mo ago First seen · 12 lines scan A 5c89616fcc94
completely is a plugin published in the GitHub repository 23ag1/completely (6 stars, last pushed 4mo ago), 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-08-31.
Other plugins, from other repositories
mean-tester
Mean tests another agent through readonly probes or marked actions on admitted test installations, checks owned approvals and state, and reports a computed ship verdict. It files nothing and fixes nothing.
scout
Autonomous knowledge management and daily briefing system. Monitors your work tools (Slack, Calendar, Linear, GitHub, etc.), synthesizes findings into a persistent knowledge base with a formal ontology, and delivers daily action items — all running unattended via scheduled Claude Code sessions. Six session types…
harnessay
Profile Claude Code and Codex transcripts: context budget reports, before/after comparisons, source evidence, and skill regression tests. Local-only, stdlib-only.
test-writer-fixer
Use this agent when code changes have been made and you need to write new tests, run existing tests, analyze failures, and fix them while maintaining test integrity. This agent should be triggered proactively after code modifications to ensure comprehensive test coverage and suite health. Examples:\n\n \nContex.
cc-autopilot
Autonomous judge agents fix your app's debt, build what's missing, and verify every change through a browser or gate suite before it lands, then find the next thing and keep going until you say stop. Each fixer owns a file-disjoint slice of the tree, so no two can ever collide, and nothing unverified reaches git. A…
ganvil
Long-running autonomous coding harness with Planner-Generator-Evaluator architecture and Sprint decomposition. Builds complete applications from simple descriptions.