ci

ci is a command for Claude Code from PMDevSolutions/Aurelius. It costs 0 tokens per session (829 once invoked), scanned A, original, MIT.

A set of repository-structure rules for a backend monorepo, a repository containing multiple related packages or projects. It defines where backend code and translation files belong and which agent must handle translation changes.

In plain words
What is it for?
Use it when locating backend code, handling internationalization files, or deciding whether a frontend change belongs in another repository.
Why use it?
It prevents searches and edits from crossing repository boundaries or bypassing the required translation workflow.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Not installable on its own: it runs a file from its repository that does not travel with it. Clone the repository, or install whatever ships that file. The line is ./scripts/verify-all.sh --ci $ARGUMENTS.

Install

Getting it into your agent

There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.

Made for: Claude Code.

Wrote 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.

agentmods badge for ci

README.md
[![agentmods](https://agentmods.dev/badge/commands/pmdevsolutions/aurelius/ci.svg)](https://agentmods.dev/commands/pmdevsolutions/aurelius/ci)
Your own site
<a href="https://agentmods.dev/commands/pmdevsolutions/aurelius/ci"><img src="https://agentmods.dev/badge/commands/pmdevsolutions/aurelius/ci.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 829 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00829
Opus 5 $0.00000 $0.00415
Sonnet 5 $0.00000 $0.00166
Haiku 4.5 $0.00000 $0.00083

Measured yesterday against content hash 0f7f067243c4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

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 yesterday.

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.

.claude/commands/ci.md · 95 lines

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

Read the full file on GitHub · 95 lines

Changes

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.

  1. yesterday First seen · 95 lines · 0 tokens per session scan A 0f7f067243c4

Subscribe to this mod's changes

ci is a command published in the GitHub repository PMDevSolutions/Aurelius (8 stars, last pushed 21d ago), 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.

Related

Other commands, from other repositories

figma-start

디자이너가 개발자의 원본 PR 위에서 검수를 시작할 때 호출하는 커맨드입니다. PR 링크 하나만 주면 프로젝트 클론부터 합니다 — 검수할 프로젝트를 미리 받아둘 필요가 없습니다. 브랜치 생성·체크아웃 후 빌드해서 기기에 올려 화면까지 띄워줍니다 — 실행할 기기·에뮬레이터가 없으면 검수에 맞는 걸 설치해서 만듭니다. 그 브랜치의 커밋 이력 패널도 개발툴에 띄워줍니다 — 지금까지 반영한 검수 내용을 검수 내내 옆에 두고 볼 수 있습니다. 커밋·푸시는 하지 않습니다. 디자이너가 화면을 먼저 확인한 뒤, 필요하면 /figma-apply로 피그마 변경을 반영합니다.

naver/design-to-ui · 49 tokens

handoff

디자이너 작업 완료 신호 — design/ 브랜치로 dev 브랜치 타겟 PR을 만들고, 원본 dev PR 작성자를 리뷰어로 지정.

naver/design-to-ui · 38 tokens

figma-apply

피그마 변경을 현재 design/ 브랜치에 반영(커밋·푸시). /figma-start 이후에 사용.

naver/design-to-ui · 31 tokens

test

Run tests and ensure code quality for the Figma Console MCP server.

southleft/figma-console-mcp · 0 tokens

design-tutorial

Interactive guided tour of Naksha — learn commands through real exercises, discover workflows, and get oriented in under 10 minutes.

Adityaraj0421/naksha-studio · 28 tokens

figma-component-library

Generate a complete component library in Figma from a design system config — atoms, molecules, and organisms with all variants, auto layout, and component properties.

Adityaraj0421/naksha-studio · 35 tokens