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 skills/stoa-platform/stoa/ci-fixnpx skills add stoa-platform/stoa --skill ci-fixgit clone --depth 1 https://github.com/stoa-platform/stoaWhat 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.00026 | $0.01183 |
| Opus 5 | $0.00013 | $0.00592 |
| Sonnet 5 | $0.00005 | $0.00237 |
| Haiku 4.5 | $0.00003 | $0.00118 |
Grade A, and why
ci-fix 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 3d 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI Fix — Auto-remediate CI Failures
Context dynamique
- Branch courante: !
git branch --show-current - Checks PR en cours: !
gh pr checks 2>/dev/null | head -20 - Workflows recents: !
gh run list --limit 5 --json name,status,conclusion,headBranch --template '{{range .}}{{.name}} | {{.status}} | {{.conclusion}} | {{.headBranch}}{{"\n"}}{{end}}' 2>/dev/null
Instructions
Auto-fix CI failure for: $ARGUMENTS
Step 1: Identify failing checks
If PR number:
gh pr checks $ARGUMENTS
gh run list --branch $(gh pr view $ARGUMENTS --json headRefName -q .headRefName) --limit 3
If workflow run URL or ID:
gh run view $ARGUMENTS --log-failed
Step 2: Read error logs
# Get the failed run ID, then read logs
gh run view <run-id> --log-failed 2>&1 | head -200
Step 3: Classify — auto-fixable or manual?
Auto-fixable (proceed to Step 4):
| Check | Error pattern | Fix command |
|---|---|---|
| Python lint (ruff) | Found N errors |
cd <component> && ruff check --fix . |
| Python format (black) | would reformat |
cd <component> && black . |
| Python import order | I001 |
cd <component> && ruff check --fix --select I . |
| TS/JS lint (eslint) | N problems (N errors, N warnings) |
cd <component> && npm run lint -- --fix |
| TS/JS format (prettier) | Code style issues |
cd <component> && npx prettier --write . |
| Rust format | Diff in |
cd stoa-gateway && cargo fmt |
| Rust clippy (simple) | warning: with help: ... suggestion |
cd stoa-gateway && cargo clippy --fix --allow-dirty |
NOT auto-fixable (report and STOP):
| Category | Examples |
|---|---|
| Logic errors | Test assertions failing, wrong behavior |
| Test failures | vitest/pytest/cargo test failures |
| Security issues | Gitleaks, Bandit findings, SAST violations |
| Type errors (complex) | Missing interfaces, wrong generics |
| Build errors | Missing dependencies, Docker build failures |
| Infrastructure | K8s deploy, ArgoCD, Helm 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.
- 3d ago First seen · 139 lines · 26 tokens per session scan A 6eb5f023cc74
ci-fix is a skill published in the GitHub repository stoa-platform/stoa (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 26 tokens to every session and 1,183 once invoked, about $0.0001 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-31.
Other skills, from other repositories
lyrik
Security assessment of a codebase — minimal mode for runner validation.
librarian
Read-only retrieval over the daily-digest kept set. Slash-invoke with /librarian ; returns items verbatim with citations.
notes
Create and manage text notes in the workspace.
tdx-assets
Look up staff devices, assets, and locations in TeamDynamix (TDX). Given a list of names, emails, or partial identifiers, resolve each person and return the assets assigned to them with location, model, ownership type, and status. Read-only.
aggregator
Daily fetch from a fixed public allowlist; score against the user's interests file; cluster into themes; push the digest to the configured channel.
csv-tools
Parse and analyze CSV data.