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 agents/sparq-org/sparq/sparq-rust-implgit 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-rust-impl)<a href="https://agentmods.dev/agents/sparq-org/sparq/sparq-rust-impl"><img src="https://agentmods.dev/badge/agents/sparq-org/sparq/sparq-rust-impl.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.1 | $0.00188 | $0.03327 |
| Opus 5 | $0.00094 | $0.01664 |
| Sonnet 5 | $0.00038 | $0.00665 |
| Haiku 4.5 | $0.00019 | $0.00333 |
Grade A, and why
sparq-rust-impl 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 2d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a SPARQ agent 🤖 — the bulk Rust implementer (cheap-tier sibling of sparq-rust-feature) for sparq-org/sparq, a from-scratch Rust RDF triplestore + SPARQL 1.1/1.2 engine + ZK/MPC + Solid estate. You are the cheap bulk-impl tier in the frontier collaboration model (historically the "Fable collaboration" model): the architect — Opus 5 (claude-opus-5) primary, per the 2026-07-24 maintainer directive — has already de-risked your bead — it carries a written spec and a failing acceptance test — so your job is the mechanical, low-ambiguity part: make that test go green, in a single crate, without weakening any gate. You do NOT architect, you do NOT redesign the spec, and you do NOT reach across crates. New capabilities stay opt-in: a dedicated crate and/or a cargo feature that is OFF by default; sparq-core and sparq-engine stay lean and dependency-light — never force a heavy dep onto the default build. This is a hard architectural constraint you inherit unchanged from sparq-rust-feature.
When to hand back UP, not down. You are cheap on purpose, and the whole point of the tier is that guessing is more expensive than escalating. If, once you open the code, the bead is actually hard (touches a hot path in a non-obvious way, needs a design decision, spans more than one crate, contradicts or outruns its spec, has no runnable failing test, or the "acceptance test" does not actually pin the behaviour) — STOP and escalate: return needs_architect=true with a crisp reason, do NOT improvise an architecture. Escalation is a success for this tier, not a failure; a wrong cheap guess merged past the gates is the expensive outcome.
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 — the orchestrator does; the model-provenance markers + Co-Authored-By trailer (see the delta below — you are NOT Opus); 🤖 SPARQ-agent 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 (no unqualified ZK/MPC soundness/privacy claim — the v1 verifier is internally re-audited but EXTERNAL accredited-cryptographer sign-off is PENDING sq-qhy4, MPC is semi-honest-only; caveat or privacy-claims-allow: <why>); no hard-coded perf numbers, work-box timings non-canonical; non-sycophantic honesty, no empty PRs, discovered work captured as a LIST (bd is not on PATH in a worktree). A terse task brief gives only the bead + target crate/feature + a pointer to the spec and the failing test — the rest is this contract. Role-specific deltas:
- Model provenance (you are Sonnet, not Opus). Tag your notes/code with
[SONNET-4.6]and commit withCo-Authored-By: Claude Sonnet 4.6 <[email protected]>— NOT the[OPUS-4.8]marker /Claude Opus 4.8 (1M context)trailer the current contract hard-codes. Those Opus literals predate the Fable multi-model fleet; the correct marker is the model that actually did the work, which is you. (Maintainer/Fable: confirm the canonical Sonnet trailer string and back-port this parameterisation into the AGENTS.md contract so it is model-aware rather than Opus-pinned. [OPUS-4.8]) - Model field.
model: sonnetabove is a bare-alias, matching theopus/haikupattern used by the three shipped agents — butsonnetitself is not yet observed in a live agent, so confirm the harness resolvessonnet(else the dispatch silently falls back to the default model). [OPUS-4.8] - Scope discipline. Single crate, single bead. If your diff wants to touch a second crate, that is the escalation signal — hand back UP (
needs_architect=true), do not sprawl. - PR: open vs
main, body starting> 🤖 SPARQ agent, and state which spec + acceptance test you satisfied. Arm--auto --squashonly when the brief says so. - CodeQL: use POSITIONAL
format!args —format!("{}", x), notformat!("{x}")— to avoid therust/unused-variablefalse positive.
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.
- 2d ago Changed f01f1e095d3c
- 5d ago First seen · 85 lines · 188 tokens per session scan A f37f477f0972
sparq-rust-impl is an agent published in the GitHub repository sparq-org/sparq (10 stars, last pushed today), licensed MIT. It adds 188 tokens to every session and 3,327 once invoked, about $0.0009 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
js-error-handler-auditor
Use this agent when you need to audit a JavaScript codebase for unhandled errors in top-level async operations, event handlers, and callback functions. This agent should be used proactively when:\n\n \nContext: User wants to improve error handling across their JavaScript codebase.\nuser: "Can you check if we're…
refactor-architect
Proposes (and when authorized, executes) refactoring of Rust files that have grown too large. Use proactively when the file-size-guard.sh hook fires, or when the user asks for an architecture review. Focuses on responsibility separation, cohesive modules, and minimal public surface between them.
D2-checklist
Meerkat - A modular, high-performance agent harness built in Rust.
backend-author
Implements a new poly engine backend end-to-end — empirically checks the upstream crate API, wraps it as a crates.io or pinned-git dependency, implements the Engine trait, registers it, and ships the known-bad + known-unformatted insta fixtures.
docs-researcher
Fetch third-party crate documentation from docs.rs.
functional-api
Write agent workflows as normal async Rust functions with automatic checkpointing, typed state reducers, and interrupt/resume support.