Borrowing it
Nothing to install: this file belongs to KhourySpecialProjects/odyssey. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/KhourySpecialProjects/odyssey/production/.claude/commands/ci.mdgit clone --depth 1 https://github.com/KhourySpecialProjects/odysseyWrote 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/commands/khouryspecialprojects/odyssey/ci)<a href="https://agentmods.dev/commands/khouryspecialprojects/odyssey/ci"><img src="https://agentmods.dev/badge/commands/khouryspecialprojects/odyssey/ci/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/commands/khouryspecialprojects/odyssey/ci"><img src="https://agentmods.dev/badge/commands/khouryspecialprojects/odyssey/ci.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.00000 | $0.00981 |
| Opus 5.5 | $0.00000 | $0.00392 |
| Sonnet 5.5 | $0.00000 | $0.00196 |
| Haiku 4.5 | $0.00000 | $0.00098 |
Grade A, and why
ci 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 today.
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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run CI Locally
Run the same checks that GitHub Actions runs on pull requests. Capture output for debugging. If anything fails, show enough context to diagnose the problem without flooding the conversation with noise.
Mode: $ARGUMENTS
If no mode specified or "full", run all checks. If "quick", skip builds.
Checks (run in order)
Run each check below. For EACH check:
- Capture both stdout and stderr
- If it passes: report ✓ and move to the next check
- If it fails: report ✗, show the RELEVANT output (see output rules below), then continue to the next check (don't stop on first failure)
1. Prettier
npx prettier . --check 2>&1 | tail -30
On failure: the output lists which files aren't formatted. Show the file list.
Then auto-fix: run npm run prettier-write and note that files were fixed.
2. ESLint
npm run lint 2>&1
On failure: ESLint output can be very long. Show only:
- The total error/warning count (last line of output)
- The first 5 files with errors
- For each file: the first 3 errors only
Do NOT dump the full ESLint output. If there are more than 15 errors, say "[N] total errors across [M] files — showing first 5 files" and truncate.
3. Frontend Tests
cd frontend && npm test -- --verbose 2>&1
On failure: Jest output is noisy. Extract and show only:
- Which test suites failed (file names)
- Which individual tests failed (test names + short error message)
- The "Tests:" summary line (X passed, Y failed, Z total)
Do NOT show passing tests. Do NOT show full stack traces unless there are fewer than 3 failures. For stack traces, show only the first 5 lines.
4. Frontend Build (skip if mode is "quick")
cd frontend && npm run build 2>&1 | tail -40
On failure: Next.js build errors are usually TypeScript errors. Show:
- The "Type error:" lines
- The file path and line number for each error
- Truncate after 10 errors
5. Backend Build (skip if mode is "quick")
cd backend && npm run build 2>&1 | tail -40
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.
- today First seen · 139 lines · 0 tokens per session scan A c75daec150b8
ci is a command published in the GitHub repository KhourySpecialProjects/odyssey (7 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 981 tokens. 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-10-02.
Other commands, from other repositories
dart-fix-ci
Command "dart-fix-ci" from dartsim/dart, covering required reading, workflow and output.
domains
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
access
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
check-release-health
Summarize the CI health of an OpenShift release using live data from the openshift-ci-mcp server.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
analyst
Use when performing local analyst review before pushing PR changes. Assesses code quality, impact analysis, and maintainability.