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 KingGyuSuh/codex-goal-in-cc/plugin install codex-goalWrote 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/kinggyusuh/codex-goal-in-cc/run-file)<a href="https://agentmods.dev/skills/kinggyusuh/codex-goal-in-cc/run-file"><img src="https://agentmods.dev/badge/skills/kinggyusuh/codex-goal-in-cc/run-file/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/kinggyusuh/codex-goal-in-cc/run-file"><img src="https://agentmods.dev/badge/skills/kinggyusuh/codex-goal-in-cc/run-file.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.00029 | $0.00475 |
| Opus 5 | $0.00015 | $0.00237 |
| Sonnet 5 | $0.00006 | $0.00095 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
run-file 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 12d 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
Run Codex Goal (Brief File)
The first whitespace-separated token in the arguments is the path to a brief markdown file (audit, spec, requirements, checklist); the rest is an optional short instruction that references the brief. Quote the path if it contains spaces (e.g. "my brief.md" Adopt items 1-4 only). The plugin does not read the brief — Codex reads it on its own turns, which is what keeps the /goal text short enough to clear the budget guard.
Before running, scan the short instruction for numeric budget phrasing like "max 500 turns" or "under 50k tokens" — Codex's goal manager misreads those as its own budget limits and can abort. Replace with task-decomposition phrasing such as "if blocked on an item, record it as unresolved and move on" or "sequential local commits, one item at a time".
Run:
node "${CLAUDE_PLUGIN_ROOT}/scripts/codex-goal.mjs" run-file "$ARGUMENTS"
Show the command stdout to the user verbatim. A footer line containing the word Goal and an elapsed time (Goal usage: <N> seconds., Goal complete; time used: <N> seconds., Goal 사용량: <N>초. — the literal phrasing varies by prompt language and Codex emits more than one form even within a single locale) plus an earlier "Goal registered…" / "목표를 등록…" line means goal mode activated. If neither shows up, Codex fell back to a plain prompt — the work still ran, but the goal lifecycle did not engage. Relay non-zero exit codes with the stderr and stop. The most common failures here are "brief file not found" and "brief path is not a regular file" — both raised by the wrapper before codex is even spawned.
Do not run another goal dispatch unless the user explicitly asks for another attempt — each one consumes Codex agent tokens against the user's usage limits.
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.
- 12d ago First seen · 22 lines · 29 tokens per session scan A 30b2d4a2fa99
run-file is a skill published in the GitHub repository KingGyuSuh/codex-goal-in-cc (5 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 29 tokens to every session and 475 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…