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/antosubash/simplemodule/cigit clone --depth 1 https://github.com/antosubash/SimpleModuleWrote 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/antosubash/simplemodule/ci)<a href="https://agentmods.dev/commands/antosubash/simplemodule/ci"><img src="https://agentmods.dev/badge/commands/antosubash/simplemodule/ci.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.00000 | $0.00350 |
| Opus 5 | $0.00000 | $0.00175 |
| Sonnet 5 | $0.00000 | $0.00070 |
| Haiku 4.5 | $0.00000 | $0.00035 |
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.
What it actually says
Run all CI checks locally, mirroring the GitHub Actions CI pipeline. This catches issues before creating a PR.
Execute these steps in order, stopping on first failure. Report results as a summary table at the end.
Step 1: Lint & Format Check
Run npm run check from the project root. This runs biome lint + format check, page validation (validate-pages), i18n validation (validate:i18n), framework-scope validation (validate:framework-scope), and TypeScript type checking (typecheck).
Step 2: Frontend Build
Run npm run build from the project root. This builds all module frontend assets via Vite in production mode.
Step 3: .NET Build
Run dotnet build from the project root. This compiles all .NET projects including source generators.
Step 4: .NET Tests
Run dotnet test --no-build from the project root. This runs all unit and integration tests (excluding load tests which are filtered out in CI).
Step 5: E2E Smoke Tests
Run npm run test:smoke -w tests/e2e to execute Playwright smoke tests. Playwright browsers are already installed.
Reporting
After all steps complete (or on first failure), print a summary table:
| Step | Status |
|---|---|
| Lint & Format | pass/fail |
| Frontend Build | pass/fail |
| .NET Build | pass/fail |
| .NET Tests | pass/fail |
| E2E Smoke Tests | pass/fail |
If any step fails, show the relevant error output and suggest a fix.
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 · 38 lines · 0 tokens per session scan A c851f741b10a
ci is a command published in the GitHub repository antosubash/SimpleModule (5 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 350 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
monitor-ci
You are the orchestrator for monitoring Nx Cloud CI pipeline executions and handling self-healing fixes. You spawn the ci-monitor-subagent subagent to poll CI status and make decisions based on the results.
actions
Command "actions" from openclaw/crabbox, covering actions, subcommands, hydrate, register and dispatch.
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.