Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add SyloRei/claude-godmode/plugin install claude-godmodeWrote 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/sylorei/claude-godmode/mission)<a href="https://agentmods.dev/skills/sylorei/claude-godmode/mission"><img src="https://agentmods.dev/badge/skills/sylorei/claude-godmode/mission/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/sylorei/claude-godmode/mission"><img src="https://agentmods.dev/badge/skills/sylorei/claude-godmode/mission.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.00079 | $0.03603 |
| Opus 5 | $0.00039 | $0.01801 |
| Sonnet 5 | $0.00016 | $0.00721 |
| Haiku 4.5 | $0.00008 | $0.00360 |
Grade A, and why
mission 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mission
Establish the durable foundation for a named feature cycle — a mission: why it exists, the constraints it must respect, what success looks like, and a numbered roadmap of work units. Run /mission <feature name> to create-or-switch a mission; re-run any time to update its direction. Every later step (/brief N, /plan N, /build N, /verify N, /ship) reads this shared context for the active mission. If /ideate already proposed this feature, /mission picks up that proposal as seed context (see step 2).
A mission is a named feature cycle stored at .planning/missions/<mission_id>/, where <mission_id> is NN-slug (allocated by bin/godmode-mission). Each mission owns its own roadmap and briefs, and its work units number from 1 within the mission.
Artifacts live in the consumer's repo (the project you are helping build), never in the plugin source. Two are project-global at the .planning/ root and span every mission; one is mission-scoped:
.planning/PROJECT.md(root, global) — purpose, constraints, success criteria. The persistent project charter, shared by all missions..planning/STATE.md(root, global) — workflow state, including the activemission_id..planning/missions/<mission_id>/ROADMAP.md(per-mission) — this mission's numbered list of work units. Each entry is referenceable by number:/brief Nplans entry N of the active mission.
Auto Mode
Auto Mode suppresses confirmation prompts ("proceed? / shall I write it?") — never the clarifying questions that decide what the project actually is. A charter built on silent guesses is confidently wrong, and every later step inherits the error. So even in Auto Mode:
- Still ask the consequential questions — the ones whose answer materially changes the charter or this mission's scope (who it's for, what "success" concretely means, hard constraints, scope edges) AND that the repo/README/manifests/recent commits cannot answer. Batch them up front, lettered/option style, so they're answered fast.
- Assume the trivial — for low-stakes gaps the repo can reasonably imply, pick a sensible default and record it under an Assumptions heading rather than asking.
- Don't interrogate: if the repo already answers something, don't ask it. Treat user course-corrections as normal input.
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.
- 9d ago First seen · 222 lines · 79 tokens per session scan A 0bdbc5179fff
mission is a skill published in the GitHub repository SyloRei/claude-godmode (3 stars, last pushed 3mo ago), licensed MIT. It adds 79 tokens to every session and 3,603 once invoked, about $0.0004 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 skills, from other repositories
asana
Manage Asana tasks and projects from the terminal. Use the timwehrle/asana CLI for common operations and direct REST API calls for section/kanban moves. Invoke with /asana.
tackle-issue
Start-of-work triage in this monorepo. Trigger on: a GitHub issue number ("tackle issue 99", "work on #42", bare #N), pasted proposal/spec text ("investigate this", "pressure-test this", "scope this"), or picker phrasing ("tackle the next issue", "what should I work on"). Read-only investigation that tries to falsify…
stale-proposals
Audit this repository's local proposal queue for stale entries: proposals still marked proposed, deferred, or accepted even though the work already shipped, plus old proposals whose subject has become inert. Reconcile proposals against plugin changelogs and first-parent Git history, automatically resolve only…
add-source
Interactively add a new source to feed-sources.md with type inference, https and name-uniqueness validation, and category checking against feed-categories.md. Appends a formatted row to the Active Sources table. Invoke with /feed-hermit:add-source.
plan-to-tasks
Transform a plancreation planv{N}.md into a structured tasks.yaml + per-WP workpackages/.yaml using parallel Sonnet sub-agents. Use after plan-creation finishes when you need execution-friendly task structure.
debt-ops-add
Register a deferred decision in the tech-debt registry. Trigger by judgment, not a marker scan, whenever a future reader would ask "why this way?": an unmade decision, stub, loosened type, bypassed check, swallowed error, a default picked "for now", or a TODO/FIXME/HACK/XXX marker. Trigger immediately whenever you…