Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/entropy-cloud/attractor-guided-engineering-templatenpx agentmods add skills/entropy-cloud/attractor-guided-engineering-template/mission-driverWrote 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/entropy-cloud/attractor-guided-engineering-template/mission-driver)<a href="https://agentmods.dev/skills/entropy-cloud/attractor-guided-engineering-template/mission-driver"><img src="https://agentmods.dev/badge/skills/entropy-cloud/attractor-guided-engineering-template/mission-driver/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/entropy-cloud/attractor-guided-engineering-template/mission-driver"><img src="https://agentmods.dev/badge/skills/entropy-cloud/attractor-guided-engineering-template/mission-driver.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Memory Poisoning · line 298 Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
- medium MCP Rug Pull · line 200 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00199 | $0.05347 |
| Opus 5.5 | $0.00080 | $0.02139 |
| Sonnet 5.5 | $0.00040 | $0.01069 |
| Haiku 4.5 | $0.00020 | $0.00535 |
Grade A, and why
mission-driver 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.
How it starts
The opening of the file, as written. The whole thing — 420 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mission-driver — Roadmap creation and mission execution
This skill operates the tools/mission-driver/ engine shipped with this repo. It is
stack-agnostic: it works for Node, Python, Java, Go, or any project whose
verification commands can be expressed as shell strings. Project-specific values
(test command, module layout, commit format) are read from missions/base.json,
docs/context/project-context.md, and AGENTS.md rather than hardcoded here.
Companion docs (read on demand, not all at once):
tools/mission-driver/docs/user-manual.zh.md/user-manual.en.md— full training handbooktools/mission-driver/README.md— command cheat-sheettools/mission-driver/EXECUTION-PRINCIPLE.md— internal execution deep divetools/mission-driver/TROUBLESHOOTING.md— diagnostics when stuckdocs/plans/00-plan-authoring-and-execution-guide.md— plan format and lifecyclereferences/mission-config-schema.md— full mission.json schema (companion to this file)references/roadmap-template.md— roadmap structure with annotated example
Mental model
A mission = a fixed config (missions/<name>.json) for one development goal. The
engine reads it and enters a loop:
CHECK (health: tests/build pass)
→ REVIEW_PLANS (review draft plans → promote active; empty forEach = passthrough)
→ EXEC_PLANS (one plan-execution subflow per active plan:
EXECUTE → CLOSURE_SCRIPT_CHECK → CLOSURE_AUDIT → BUILD_VERIFY)
→ DRAFT_PLANS (draft 1-3 plans from roadmap → sub-agent review → promote active)
→ [loop back to REVIEW_PLANS]
→ nothing to draft → DEEP_AUDIT (multi-audit + open-audit → draft remediation plans)
→ REVIEW_PLANS (execute audit-created plans)
→ ... until maxAuditRounds exhausted and nothing outstanding
Key facts:
- Roadmap precedes mission. The
draftcommand will generate both roadmap andmissions/<name>.jsonfrom a single description, but only after the brief stage confirms scope is clear. missions/<name>.jsonis pure static config — no runtime state. The engine's runtime state lives in_tmp/<runDir>/run-state.json.- Every AI step is a child
opencode runprocess; logs land in_tmp/<ts>-mission-driver/. - Plan lifecycle:
draft→ (REVIEW_PLANS) →active→ (EXEC_PLANS) →completed. Subflowplan-executionruns once per active plan. - Ctrl-C / SIGTERM is caught by
main.jsfor graceful process-tree cleanup. - Plan format is a fixed contract enforced by
tools/mission-driver/src/plan-check.mjs.
What ships with it
2 files 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.
- 1mo ago First seen · 420 lines · 199 tokens per session scan A 554af2d42510
mission-driver is a skill published in the GitHub repository entropy-cloud/attractor-guided-engineering-template (81 stars, last pushed 1mo ago), licensed MIT. It adds 199 tokens to every session and 5,347 once invoked, about $0.0008 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-08-30.
Other skills, from other repositories
om-auto-continue-pr
Resume any open PR — started by om-auto-create-pr or opened outside the pipeline. Claims it, resumes in an isolated worktree from the first unchecked step of its execution plan; a PR with no plan is adopted — the goal is reconstructed from its description, comments, review feedback, linked issues and diff, then…
om-auto-fix-issue
Fix or implement a tracker issue end to end from a single command — takes an issue id or a plain problem description (filed first via om-prepare-issue), classifies, then drives the bug autofix chain (om-verify-in-repo, om-root-cause, om-fix, om-open-pr, om-auto-review-pr, om-auto-qa-pr for UI fixes) or the feature…
om-spec-writing
Write and review feature specifications to staff-engineer standards. Skeleton-first drafting with a hard Open Questions gate, research against market leaders, an implementation breakdown into phases and steps that feeds om-auto-create-pr, and a severity-ranked architectural review format. Use when starting a new spec…
om-setup-discovery-pipeline
Adds the product layer to a repository that om-setup-agent-pipeline already configured — one yes per product role, a discovery block in .ai/agentic.config.json, the Discovery stage, Definition of Ready, product roles, and protected product decisions appended to SDLC.md between markers, the research directory, and a…
om-fix
Implements the minimal code change identified by the om-root-cause step, adds regression tests, and runs the configured validation gate. Claims the tracker issue at start (assignee + in-progress label + claim comment) so concurrent automation backs off. Does not commit, push, or open a PR — that is the om-open-pr…
om-help
Read-only router for "which skill should I use?", "what do I do next?", "how do I do X here?". Builds the answer at run time from the repo's AGENTS.md Task Router, the skills actually installed, optional repo workflow data, and knowledge sources — then recommends and hands back control. Never runs the pipeline itself.