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/doodledood/manifest-devWrote 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/doodledood/manifest-dev/manifest-dev-tools)<a href="https://agentmods.dev/plugins/doodledood/manifest-dev/manifest-dev-tools"><img src="https://agentmods.dev/badge/plugins/doodledood/manifest-dev/manifest-dev-tools/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/doodledood/manifest-dev/manifest-dev-tools"><img src="https://agentmods.dev/badge/plugins/doodledood/manifest-dev/manifest-dev-tools.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
manifest-dev-tools 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 2d 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": "manifest-dev-tools",
"version": "6.5.2",
"description": "Tools for prompts and PRs alongside the manifest workflow. Includes collaborative PR walkthroughs, autonomous PR review that independently re-verifies a manifest gate by gate, author-side PR babysitting that drives the lifecycle toward green and mergeable, gap-calibrated prompt engineering, standalone goals distilled from Manifests, cross-boundary context handoff, incremental teaching, and an eli5 explainer that renders any topic as big pictures and few words.",
"keywords": [
"post-processing",
"manifest",
"pr-review",
"walk-pr",
"walkthrough",
"autonomous-review",
"review-loop",
"babysit-pr",
"pr-lifecycle",
"prompt-engineering",
"manifest-to-goal",
"prompts",
"handoff",
"context-handoff",
"teaching",
"teach-me",
"learning",
"session-explanation",
"eli5",
"explainer"
]
}
What it installs
The manifest is a name and a version. 12 skills travel with it, and installing the plugin installs all of them — 808 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill babysit-pr A 59 tokens
- Skill review-pr-judgment A 63 tokens
- Skill review-pr A 75 tokens
- Skill prompt-engineering A 56 tokens
- Skill walk-pr A 89 tokens
- Skill review-pr-holistic A 74 tokens
- Skill manifest-to-goal A 45 tokens
- Skill review-pr-thread-verify A 63 tokens
- Skill review-prompt A 60 tokens
- Skill teach-me A 121 tokens
- Skill handoff A 64 tokens
- Skill eli5 A 39 tokens
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.
- 2d ago Changed 18e36b29b367
- 11d ago Changed b1537927b07d
- 12d ago Changed · +1 lines 96e8bd42d351
- 15d ago Changed 53825e881a77
- 20d ago Changed e734d3ef1741
- 1mo ago Changed 080c967cafa5
- 1mo ago Changed cf649262c855
- 1mo ago Changed 0c2c308845c6
- 1mo ago Changed a636790b54a6
- 1mo ago First seen · 27 lines scan A 0f8401889dc2
manifest-dev-tools is a plugin published in the GitHub repository doodledood/manifest-dev (75 stars, last pushed 2d 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-30.
Other plugins, from other repositories
github
Skills for GitHub pull request workflows — creating PRs, addressing review feedback, and resolving threads.
han-github
Github specific extensions to the Han plugin for agentic planning and coding. Provides skills to post code reviews as PR comments, update a PR description with a consistent format, etc.
odin-git
ODIN workflows for commits, branches, pull requests, review feedback, and issue tracking.
pull-request
Pull request workflows: create, update, babysit CI, and reviewer follow-up.
misuzu
Respond to PR review comments semi-automatically. Splits review findings into logical units, fixes and commits them one by one, then replies and resolves review threads.
coding
Opinionated Claude Code workflow skills: clear and unambiguous technical writing (write-clearly), iterative planning (replan), proof-based code review (review, review-staged, second-opinion), disciplined Conventional-Commit staging (gitplan, stage), finding the session that wrote an uncommitted change (find), and the…