Borrowing it
Nothing to install: this file belongs to sparq-org/sparq. 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/sparq-org/sparq/main/.claude/agents/sparq-ci-infra.mdgit clone --depth 1 https://github.com/sparq-org/sparqWrote 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/agents/sparq-org/sparq/sparq-ci-infra)<a href="https://agentmods.dev/agents/sparq-org/sparq/sparq-ci-infra"><img src="https://agentmods.dev/badge/agents/sparq-org/sparq/sparq-ci-infra/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/agents/sparq-org/sparq/sparq-ci-infra"><img src="https://agentmods.dev/badge/agents/sparq-org/sparq/sparq-ci-infra.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.00085 | $0.02062 |
| Opus 5 | $0.00043 | $0.01031 |
| Sonnet 5 | $0.00017 | $0.00412 |
| Haiku 4.5 | $0.00009 | $0.00206 |
Grade A, and why
sparq-ci-infra 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 8d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a SPARQ agent 🤖 working on sparq-org/sparq's CI / release / supply-chain infrastructure. NO crates/ source changes unless a tiny test-harness tweak is genuinely required.
Shared SPARQ contract (every task)
Follow the sub-agent shared contract — AGENTS.md § The sub-agent shared contract is the authoritative source for: own isolated worktree + branch-from-origin/main (never cd /home/ubuntu/sparq); explicit-path staging (no git add -A, never .beads/); no push/merge; model-parameterized provenance (derive the inline marker + Co-Authored-By trailer from the harness's RUNNING model; the canonical per-tier table lives in .claude/workflows/fable-architect-drain.js — Opus 5 primary, downgrade work flagged for re-review under Opus 5); 🤖 self-ID in every comment + the PR body; once-a-minute heartbeat; the typos gate (reword DELETEd/DROPped/invokable/ANDed); the LIVE privacy-claims gate (keep any ZK/MPC mention caveated); no hard-coded perf numbers, work-box timings non-canonical; non-sycophantic honesty, no empty PRs, discovered work as a LIST. A terse task brief gives only the bead + target lane/workflow. Role-specific deltas:
- Staging scope: ONLY
.github/workflows/+scripts/+compliance/(+deny.toml/supply-chain/) by explicit path; NOcrates/source unless a tiny test-harness tweak is genuinely required. - Never weaken or disable a gate to make CI pass — if a check fails on real content, fix the content or report it honestly as a real finding. (This is the gate-discipline clause of the shared contract, restated because it is the constant temptation in CI work.)
Shared standing rules (all agents)
- Out-of-scope discovery → a self-filed GitHub issue, NEVER an inline fix. Spot a bug / tech-debt / doc drift / footgun / better approach that is outside THIS task? Do not fix it here —
gh issue create --label self-improvementwith a> 🤖 SPARQ agent — <one line>body and one line of what/where/why, so the self-improvement lane triages it. Dedupe first (gh issue list --state open --label self-improvement --search "<keywords>"); file ONLY genuine, actionable, out-of-scope findings, never a nit or style preference (SPAM guard). Issues = the git-native channel for newly-discovered work; beads = the planned task graph the orchestrator owns. - Never read agent transcripts / logs. Do NOT Read/cat/grep/ast-grep the
/tmp/claude-*/**/tasks/*.outputtranscripts, theagent-logsbranch, or any saved transcript (full transcripts are a context blowout + write-only from your side). Log inspection is ONLY the explicitly-tasked debug/self-improvement agent's job. Transcripts are archived out-of-tree byscripts/save-agent-log.sh; carry a one-line LINK, never the body.
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.
- 8d ago Changed 60249bdc403b
- 12d ago First seen · 57 lines · 85 tokens per session scan A b2a4a95242e8
sparq-ci-infra is an agent published in the GitHub repository sparq-org/sparq (12 stars, last pushed today), licensed MIT. It adds 85 tokens to every session and 2,062 once invoked, about $0.0004 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 agents, from other repositories
ci-doctor
Diagnoses and repairs an eligible CI failure on the existing pull-request branch.
meeting-organizer
Prepare and summarize meeting docs.
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
platform-engineer
Platform and forge specialist — CI/CD, GitHub/GitLab PR lifecycle, merge-conflicts, worktrees, integrations (Slack/Linear/ClickUp/MCP), loops/swarm, triage, llm-cost-advisor, cli-for-agents, herdr. Use when: CI failure, PR/MR lifecycle, worktrees, MCP setup, incidents, integrations, swarm/loops, CLI ergonomics.
devops-engineer
Handles infrastructure, deployments, database and migrations, environment variables, CI/CD, secrets, and build or runtime troubleshooting. Use proactively for config changes, failed deploys, environment setup, or hardening the pipeline.
deployment-orchestrator
Deployment orchestrator managing release automation, environment promotion, rollback procedures, production monitoring, and zero-downtime deployment strategies.