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 skills/pejmanjohn/cc-plugin-codex/claude-resultnpx skills add pejmanjohn/cc-plugin-codex --skill claude-resultgit clone --depth 1 https://github.com/pejmanjohn/cc-plugin-codexWrote 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/pejmanjohn/cc-plugin-codex/claude-result)<a href="https://agentmods.dev/skills/pejmanjohn/cc-plugin-codex/claude-result"><img src="https://agentmods.dev/badge/skills/pejmanjohn/cc-plugin-codex/claude-result.svg" alt="Measured on agentmods" 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 | $0.00013 | $0.00178 |
| Opus 5 | $0.00006 | $0.00089 |
| Sonnet 5 | $0.00003 | $0.00036 |
| Haiku 4.5 | $0.00001 | $0.00018 |
Grade A, and why
claude-result 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 4d 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.
This is a copy
89% identical to claude-cancel — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
You are the thin skill wrapper for Claude Companion result runs.
Supported flags:
--job <id>--json
Pass only the flags listed above; the script rejects unknown flags.
- Treat the remaining user text after the skill mention as raw command arguments.
- Resolve
<plugin-root>as the directory two levels above thisSKILL.mdfile; it is the directory containingscripts/,skills/,prompts/, andschemas/. - Run
node <plugin-root>/scripts/claude-companion.mjs result <remaining arguments>from the user's current workspace. - Return stdout verbatim.
- If the command exits non-zero, surface stderr verbatim.
- Do not implement logic in this skill.
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.
- 4d ago First seen · 21 lines · 13 tokens per session scan A 2d8f5948227a
claude-result is a skill published in the GitHub repository pejmanjohn/cc-plugin-codex (9 stars, last pushed 1mo ago), licensed MIT. It adds 13 tokens to every session and 178 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to claude-cancel, differing in 8 lines, and is treated as a copy.
Other skills, from other repositories
flutter-ui
Build Flutter UI from Figma MCP or image input. Scans src for design tokens (colors, sizes, text styles), existing components, and naming conventions before writing a single line of code. Never hard-codes values.
review
Plan-aware graph-enhanced code review before merge. CRITICAL issues block merge. Use after fix/verify.
serena
Serena code intelligence — LSP-powered symbol navigation, diagnostics, and targeted code surgery. Activate before complex refactors, cross-file analysis, or when graph tools need symbol-level depth.
database-migrations
Database migration best practices for schema changes, data migrations, rollbacks, and zero-downtime deployments across PostgreSQL, MySQL, and common ORMs (Prisma, Drizzle, Kysely, Django, TypeORM, golang-migrate).
diagnose
Structured 6-phase debugging. Build feedback loop first, reproduce deterministically, hypothesize with ranked falsifiable theories, instrument one variable at a time, fix with regression test, cleanup. Use when a bug exists, tests fail unexpectedly, or behavior is wrong and cause is unknown.
execute
Dispatch and execute implementation plans with TDD and checkpoints. Use when plan is ready. Parallel by default for independent tasks.