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 doodledood/manifest-dev --skill manifest-dev-helpgit 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/skills/doodledood/manifest-dev/manifest-dev-help)<a href="https://agentmods.dev/skills/doodledood/manifest-dev/manifest-dev-help"><img src="https://agentmods.dev/badge/skills/doodledood/manifest-dev/manifest-dev-help/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/doodledood/manifest-dev/manifest-dev-help"><img src="https://agentmods.dev/badge/skills/doodledood/manifest-dev/manifest-dev-help.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.00138 | $0.02669 |
| Opus 5.5 | $0.00055 | $0.01068 |
| Sonnet 5.5 | $0.00028 | $0.00534 |
| Haiku 4.5 | $0.00014 | $0.00267 |
Grade A, and why
manifest-dev-help 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.
How it starts
The opening of the file, as written. The whole thing — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
manifest-dev-help
People come here to ask about anything in manifest-dev that they do not understand, and why it works that way. Answer each question with what the part is and why it exists. Write each answer close to ASD-STE100: short sentences, one topic in each sentence, and simple words with one meaning.
How to answer
- When the question names a term or asks about a part, file or behavior, read
references/GLOSSARY.md. - When the user asks for all the terms, give all of
references/GLOSSARY.md. - When there is no question, give What manifest-dev is for, The workflow and The autonomy ladder.
- When the user points at something, read it first: a Manifest, a log, a pull request or a file.
- When the question is about the project of the user, also read its Project Surfaces.
- When this skill does not give the answer or its reason, read the skill that owns that behavior.
- Find that skill in the folder next to this one: its
SKILL.mdand itsreferences/folder. - Answer only the question.
- Give the reason for each part, not only what it is.
- When the answer comes from a file other than this skill, name that file.
- When no file gives the answer, say so instead of a guess.
What manifest-dev is for
Agents can write almost all code now, but projects still drift. Each session must find again what the project is for, what to do next, and what "done" means. The speed of the agent then makes more work than a person can examine.
manifest-dev keeps these three things in the project, not in the head of a person. The agent reads them, does the work against them, and examines its result before it says that it is done. The promise: you give the agent a complex task, and you trust the result enough to ship it with minimal review. Weeks later, the project still knows what it is for, what is next, and what "done" means. The code is also easier to change correctly than before.
You can assign a project outcome within chosen limits. The coordinator can investigate, shape work, deliver it and read the results. You retain the decisions you want to make. Reliable ongoing operation remains an ambition; a completed task does not prove that ambition.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed · +8 lines 3e7bbbe0c787
- 5d ago Changed · +7 lines 7cd440f94218
- 8d ago First seen · 152 lines · 138 tokens per session scan A b39e71d3fea6
manifest-dev-help is a skill published in the GitHub repository doodledood/manifest-dev (75 stars, last pushed today), licensed MIT. It adds 138 tokens to every session and 2,669 once invoked, about $0.0006 per session on Opus 5.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-10-16.
Other skills, from other repositories
great_cto
Use when the CTO describes a feature, task, or project goal. Orchestrates the full SDLC pipeline automatically based on project type.
opportunity-solution-tree
Build an Opportunity Solution Tree (OST) to structure product discovery — map a desired outcome to customer opportunities, possible solutions, and experiments. Based on Teresa Torres' Continuous Discovery Habits. Use when the team is unclear what to build next, when multiple opportunities compete, or before writing a…
done-blocked
Reusable reporting contract for any agent that hands work back to the pipeline. Forces ONE of two terminal statuses (DONE or BLOCKED) with a specific evidence shape. Stops vague "probably finished" and "kind of stuck" verdicts.
outcome-roadmap
Transform an output-focused roadmap (feature list) into an outcome-focused one. Rewrites initiatives as outcome statements reflecting user and business impact. Use when a roadmap lists features instead of results, when making a roadmap more strategic, or when communicating what success looks like vs what will be built.
pm-planning
Decomposition methodology for pm agent — turns an approved ARCH document into a Beads task list with explicit dependencies, time-boxes, and acceptance criteria. The pipeline can only orchestrate work it can see; this skill defines what "seeable work" looks like.
evidence-publish
Deliver a QA/evidence packet to a tracker or keep it local, behind an always-ask preview gate. Protocol for /orc:qa Phase 6, /orc:evidence, and any evidence-delivery step.