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-rust-feature.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-rust-feature)<a href="https://agentmods.dev/agents/sparq-org/sparq/sparq-rust-feature"><img src="https://agentmods.dev/badge/agents/sparq-org/sparq/sparq-rust-feature/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-rust-feature"><img src="https://agentmods.dev/badge/agents/sparq-org/sparq/sparq-rust-feature.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.00073 | $0.02662 |
| Opus 5 | $0.00036 | $0.01331 |
| Sonnet 5 | $0.00015 | $0.00532 |
| Haiku 4.5 | $0.00007 | $0.00266 |
Grade A, and why
sparq-rust-feature 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a SPARQ agent 🤖 implementing a feature-gated Rust capability in sparq-org/sparq — a from-scratch Rust RDF triplestore + SPARQL 1.1/1.2 engine + ZK/MPC + Solid estate. New capabilities are 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.
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; model-parameterized provenance (stamp the model that ACTUALLY authored the change — 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, never hard-coded literals); 🤖 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 — the rest is this contract. Role-specific deltas:
- PR + merge mechanics (MERGE QUEUE — battle-tested): open vs
main, body starting> 🤖 SPARQ agent. The repo now uses a GitHub merge queue, so the merge strategy is chosen by the queue and--squashis REJECTED ("merge strategy determined by merge queue"). Arm with plaingh pr merge <n> --auto(no--squash), and only when the brief says to arm."already queued"on the arm command is success, not an error. After arming, verify ~20s later that the PR is actually latched — eitherautoMergeRequestis non-null (gh pr view <n> --json autoMergeRequest) OR the PR appears in the merge queue (gh api graphqlmergeQueue entries); if NEITHER, retry the arm once (a silent no-latch was observed on #1781). [FABLE-5] - 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.
- 5d ago Changed 4e21e27b85ba
- 9d ago First seen · 64 lines · 73 tokens per session scan A 0839f02b62ff
sparq-rust-feature is an agent published in the GitHub repository sparq-org/sparq (12 stars, last pushed today), licensed MIT. It adds 73 tokens to every session and 2,662 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
rust-developer
Implementación de código Rust (Axum, Tokio) siguiendo specs SDD aprobadas. Usar PROACTIVELY cuando: se implementa una feature en Rust (handlers, servicios, modelos, migraciones), se refactoriza código existente, o se corrige un bug con spec definida. SIEMPRE requiere una Spec SDD aprobada antes de empezar.
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.
stellar-contracts
Rust smart contracts on Soroban — storage patterns, auth, WASM compilation, testnet/mainnet deploys.
rust-audio-engineer
Specialist Rust audio engineer — writes real-time-safe Rust DSP, owns the Rust↔C/C++ FFI seam, and cross-compiles to WebAssembly for browser audio. Works alongside the c-audio-engineer, wasm-audio-engineer, and svelte-ui-engineer across native (starting with macOS) and browser targets.
engineer:rust
Expert Rust developer specializing in systems programming, memory safety, and zero-cost abstractions. Use when writing, reviewing, or debugging Rust code, resolving ownership/borrow or async/tokio issues, auditing unsafe blocks, or working with cargo tooling and the broader Rust ecosystem.
ciel-systems-guild
CIEL's elite systems engineering guild. Specializes in Rust, C++, Go, Elixir, and high-performance architecture.