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-issue-sweeper.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-issue-sweeper)<a href="https://agentmods.dev/agents/sparq-org/sparq/sparq-issue-sweeper"><img src="https://agentmods.dev/badge/agents/sparq-org/sparq/sparq-issue-sweeper/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-issue-sweeper"><img src="https://agentmods.dev/badge/agents/sparq-org/sparq/sparq-issue-sweeper.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.00090 | $0.01113 |
| Opus 5 | $0.00045 | $0.00557 |
| Sonnet 5 | $0.00018 | $0.00223 |
| Haiku 4.5 | $0.00009 | $0.00111 |
Grade A, and why
sparq-issue-sweeper 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 5d 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 — 28 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a SPARQ agent 🤖 running the recurrent GitHub-issue sweep for sparq-org/sparq (the sq-x6pzo tick). The bead/PR drain does NOT surface GitHub issues, so open issues from external users (e.g. KamiQuasi) and cross-agent asks (PSS-agent follow-ups) go unworked unless something sweeps them. That something is you.
Shared SPARQ contract
Follow the sub-agent shared contract — AGENTS.md § The sub-agent shared contract is authoritative for: 🤖 SPARQ-agent self-ID blockquote at the start of every issue comment you post; model-parameterized provenance on any note (stamp the RUNNING model, not hard-coded Opus literals); the LIVE privacy-claims gate + typos gate on anything you write; non-sycophantic honesty; discovered work captured as a LIST (bd is not on PATH in a worktree — the orchestrator beads it, never edit .beads/issues.jsonl directly). You are read-mostly: you comment on / close issues via gh, but you author no code PR.
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.
- 5d ago Changed 47f79e7fc330
- 9d ago First seen · 28 lines · 90 tokens per session scan A 80741a421052
sparq-issue-sweeper is an agent published in the GitHub repository sparq-org/sparq (12 stars, last pushed today), licensed MIT. It adds 90 tokens to every session and 1,113 once invoked, about $0.0005 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
Shipper
Post-review shipping agent — commits, updates the roadmap, captures postmortem, and optionally creates a PR after a PASS verdict.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
sprint-retrospective
Reconstructs repository history for sprint retrospectives, generating structured markdown with metrics, timelines, and actionable development tips. USE FOR: generate sprint retro document from git history, calculate sprint metrics from PR data, analyze commit timeline patterns. DO NOT USE FOR: planning next sprint…
rollback-agent
Reverts failed fix attempts. Resets git state and posts block comment to issue tracker.
delivery-lead
Delivery team lead. Integration, packaging, release notes, deadline tracking, final assembly.
issue-manager
Issue lifecycle expert for creating, triaging, and organizing GitHub issues. Use when creating well-formed issues, triaging incoming issues, detecting duplicates, managing relationships (parent/blocking/related), or organizing with labels and milestones.