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 agentmods add instructions/robzilla1738/supergoal/agents-mdgit clone --depth 1 https://github.com/robzilla1738/supergoalWhat 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 | $0.04178 | $0.04178 |
| Opus 5 | $0.02089 | $0.02089 |
| Sonnet 5 | $0.00836 | $0.00836 |
| Haiku 4.5 | $0.00418 | $0.00418 |
Grade C, and why
supergoal AGENTS.md scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
6. **Re-sync to Codex**: `rm -rf ~/.codex/skills/supergoal && cp -R skills/supergoal ~/.codex/skills/supergoal`, then verify byte-identical with `diff -r skills/supergoal ~/.codex/skills/supergoal`. How it starts
The opening of the file, as written. The whole thing — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Authoritative project doc. Any agent (Claude, Codex, or other) opening this repo should be able to read this file alone and understand the project, where to make changes, and what conventions to follow.
What this repo is
Supergoal is a Claude Code / Codex skill that turns a vague build request into a deeply-planned, autonomously-executed /goal run with built-in retry, fix-spec recovery, per-phase memory writeback, and a final audit pass that re-validates the work against the original plan.
- Slash command:
/supergoal <task> - Central mechanism: produces one ready-to-paste
/goalcommand. The user pastes it once; the rest is autonomous. - Works on: Claude Code (via plugin marketplace) and Codex CLI (via manual skill copy).
- Public install: see
README.md.
Repo layout
supergoal/
├── .claude-plugin/
│ ├── marketplace.json Catalog Claude Code reads when added as a marketplace
│ └── plugin.json Plugin manifest (name, version, description, skills path)
├── .gitattributes Forces `*.sh` to LF (CRLF shebangs fail on a fresh Windows checkout).
├── .gitignore Editor/OS junk + .supergoal/ artifact dirs
├── AGENTS.md This file. Authoritative project doc.
├── CLAUDE.md Claude Code-specific tips. Points at this file.
├── CHANGELOG.md Per-version release notes. Keep-a-Changelog format, SemVer.
├── LICENSE MIT.
├── README.md Public-facing: what it is, install, use, Mermaid flow charts.
├── skills/supergoal/
│ ├── SKILL.md The skill itself. ~565 lines (grew with v0.7's Stage 0 namespace-claim section; the phase-loop section duplicates PROTOCOL.md and is a candidate for slimming next release).
│ ├── references/ Progressive-disclosure docs the agent reads when needed.
│ │ ├── planning-depth.md What makes a plan deserve "super".
│ │ ├── phase-design.md How to slice phases (adaptive count, no cap).
│ │ ├── goal-format.md /goal mechanics on both hosts; required transcript blocks.
│ │ └── repo-state-comparison.md The one comparison strategy (complete working tree vs baseline).
│ ├── scripts/ Bash scripts the planner/executor run during stages.
│ │ ├── detect-env.sh Greenfield env recon.
│ │ ├── detect-stack.sh Brownfield stack/framework detection.
│ │ ├── summarize-repo.sh Compressed repo map.
│ │ ├── claim-run.sh Atomically claims a unique per-run dir under .supergoal/ (concurrent-run isolation). Tested by tests/claim-run.test.sh.
│ │ ├── repo-state.sh Complete working-tree-vs-baseline comparison (audit + cleanliness). Copied into the run's .supergoal/<run-id>/ dir at Stage 7.
│ │ └── validate-phase.sh Sanity-checks a phase spec has required markers.
│ └── templates/ Files the planner copies into a run's `.supergoal/<run-id>/` dir.
│ ├── ROADMAP.md Phase plan with dependencies.
│ ├── STATE.md Live progress file.
│ ├── phase-goal.txt Phase spec skeleton (work, criteria, evidence, commands).
│ └── PROTOCOL.md Execution loop + failure recovery + final audit protocol.
└── tests/ Repo-only (not shipped in the plugin payload).
├── claim-run.test.sh Fixture tests for claim-run.sh (incl. the concurrent-claim race).
└── repo-state.test.sh Fixture tests for repo-state.sh over throwaway git repos.
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 First seen · 190 lines · 4,178 tokens per session scan C a681abb345a8
supergoal AGENTS.md is an instructions file published in the GitHub repository robzilla1738/supergoal (666 stars, last pushed 14d ago), licensed MIT. It adds 4,178 tokens to every session, about $0.0209 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.