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 commands/xiaolai/cc-suite/resultgit clone --depth 1 https://github.com/xiaolai/cc-suiteWhat 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.00009 | $0.00561 |
| Opus 5 | $0.00005 | $0.00280 |
| Sonnet 5 | $0.00002 | $0.00112 |
| Haiku 4.5 | $0.00001 | $0.00056 |
Grade A, and why
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 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.
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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
Workflow
Step 1: Resolve the job and read its stored result
Resolve the reference (empty → most recent finished job for this session; otherwise exact or prefix match) and load the stored result in one call:
node -e "
const { resolveResultJob, readStoredJob } = await import('${CLAUDE_PLUGIN_ROOT}/scripts/lib/job-control.mjs');
try {
const reference = process.argv[1] || undefined;
const { workspaceRoot, job } = resolveResultJob(process.cwd(), reference);
const stored = readStoredJob(workspaceRoot, job.id);
console.log(JSON.stringify({ job, stored }, null, 2));
} catch (error) {
console.error(error.message);
process.exitCode = 1;
}
" -- "$ARGUMENTS"
If the command exits non-zero, relay the single-line message it printed to stderr verbatim (it already distinguishes still-running jobs, unknown references, ambiguous prefixes, and no-finished-jobs) and STOP.
Step 2: Check the stored payload
stored contains the raw Codex output and metadata. If stored is null or does not contain usable output, report Result file missing or unreadable for job {job-id} — it may have been pruned. Run /cc-suite:status to see available jobs. and STOP.
Step 3: Display the result
# Codex Result
**Job**: {id}
**Kind**: {kind}
**Status**: {status}
**Duration**: {duration}
**Thread ID**: `{threadId}` _(use `/continue {threadId}` to iterate)_
---
{raw Codex output}
---
_Job: `{id}` | Thread: `{threadId}` | Run `/continue {threadId}` to follow up._
If the job failed, show the error message instead of the raw output.
Step 4: Offer next steps
Based on the job kind:
- audit: "Fix issues with
/audit-fix, verify with/verify, or drill deeper with/continue {threadId}" - implement: "Review changes with
git diff, run tests, or continue with/continue {threadId}" - bug-analyze: "Apply the fix, or drill deeper with
/continue {threadId}" - verify: "Run
/auditfor a fresh scan, or/audit-fixto fix remaining issues"
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 · 68 lines · 9 tokens per session scan A ec0f2a172f88
result is a command published in the GitHub repository xiaolai/cc-suite (44 stars, last pushed 24d ago), licensed ISC. It adds 9 tokens to every session and 561 once invoked, about $0.0000 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-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.