Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/PMDevSolutions/Aureliusnpx agentmods add commands/pmdevsolutions/aurelius/ciWrote 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/pmdevsolutions/aurelius/ci)<a href="https://agentmods.dev/commands/pmdevsolutions/aurelius/ci"><img src="https://agentmods.dev/badge/commands/pmdevsolutions/aurelius/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/pmdevsolutions/aurelius/ci"><img src="https://agentmods.dev/badge/commands/pmdevsolutions/aurelius/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.00829 |
| Opus 5.5 | $0.00000 | $0.00332 |
| Sonnet 5.5 | $0.00000 | $0.00166 |
| Haiku 4.5 | $0.00000 | $0.00083 |
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 1mo 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ci — CI-Optimized Verification
Runs the same checks as /verify-all but in non-interactive, machine-readable mode. Designed for CI pipelines, pre-merge gates, and automation: no prompts, JSON output, exit code reflects overall pass/fail.
Usage
/ci
/ci --skip dead-code,security
/ci --include lint-and-format,types,tests
The slash command wraps ./scripts/verify-all.sh --ci. The --ci flag implies --json and sets non-interactive behavior. Pass --skip or --include to filter checks.
What runs
Same eight checks as /verify-all, in the same order:
lint-and-format → types → tests → accessibility → tokens → dead-code → security → bundle-size
bundle-size is automatically skipped when no build artifact (dist/, .next/, build/, out/) is present. No other check requires a dev server, so all of them run in CI without extra setup.
Output
JSON written to stdout:
{
"ok": false,
"summary": { "pass": 6, "fail": 1, "skip": 1, "total": 8 },
"checks": [
{ "name": "lint-and-format", "status": "pass", "exitCode": 0, "durationMs": 2618, "reason": "" },
{ "name": "types", "status": "fail", "exitCode": 1, "durationMs": 1843, "reason": "exit 1" },
{ "name": "tests", "status": "pass", "exitCode": 0, "durationMs": 4205, "reason": "" },
...
{ "name": "bundle-size", "status": "skip", "exitCode": 0, "durationMs": 0, "reason": "no build artifact (dist/.next/build/out)" }
]
}
| Field | Meaning |
|---|---|
ok |
true only when every check passed or was skipped intentionally |
summary.pass / fail / skip / total |
Counts across all checks |
checks[].status |
pass | fail | skip |
checks[].exitCode |
The exit code returned by the underlying check script |
checks[].durationMs |
Wall-clock duration |
checks[].reason |
Empty on pass; short reason on fail/skip |
Steps
1. Run the orchestrator in CI mode
./scripts/verify-all.sh --ci $ARGUMENTS
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.
- 1mo ago First seen · 95 lines · 0 tokens per session scan A 0f7f067243c4
ci is a command published in the GitHub repository PMDevSolutions/Aurelius (9 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 829 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-09-04.
Other commands, from other repositories
figma-start
A command that prepares a designer's review branch from a developer's GitHub pull request. A pull request is a proposed set of code changes, and a branch is a separate line of project history.
handoff
A handoff command that creates a pull request from a designer's working branch to the developer's branch after design changes are ready for review. A pull request is a request to inspect and merge code changes.
figma-apply
A command that applies changes from a Figma design file to the current design branch, then commits, pushes, and checks the project build. Figma is a tool for creating and sharing interface designs.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.