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 instructions/dark-builders/darq/claude-mdgit clone --depth 1 https://github.com/dark-builders/darqWrote 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/instructions/dark-builders/darq/claude-md)<a href="https://agentmods.dev/instructions/dark-builders/darq/claude-md"><img src="https://agentmods.dev/badge/instructions/dark-builders/darq/claude-md.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 | $0.01461 | $0.01461 |
| Opus 5 | $0.00731 | $0.00731 |
| Sonnet 5 | $0.00292 | $0.00292 |
| Haiku 4.5 | $0.00146 | $0.00146 |
Grade A, and why
darq CLAUDE.md 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 4d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project
darq is a Rust CLI + TUI that orchestrates spec-to-app software generation through an autonomous pipeline. It takes a GitHub issue, plans implementation via ACP-compatible AI agents, validates output through SAT (Scenario-driven AI Testing) with persona-based scoring, and feeds results back into a learning loop. Core loop: spec → plan → implement → review → merge → test → learn → repeat.
Build & Test Commands
cargo build # Build all crates (debug)
cargo build --release # Release build
cargo test # All unit tests (both crates)
cargo test -p darq-core # Core library tests only
cargo test -p darq # CLI binary tests only
cargo test test_workflow_registry # Single test by name
cargo test -p darq-core workflow:: # Tests in a module
cargo clippy --workspace # Lint
cargo fmt --check # Format check
Integration tests live in tests/ at the workspace root:
cargo test --test spine_integration
cargo test --test sweep_integration
cargo test --test workflow_integration
The binary and package are both named darq:
cargo run -- sat run --target /path/to/project
cargo run -- run issue 42 --full
Workspace Structure
Two-crate workspace:
crates/darq-core— All logic. Library crate. Usesthiserrorfor typed errors.crates/darq— Thin binary wrapper (package namedarq). Usesanyhowfor error context. Never useanyhowin darq-core.
Architecture
Daemon Model
darq uses a daemon architecture. Most CLI commands are thin clients that connect to a background daemon via Unix socket (~/.darq/daemon.sock).
darq daemon startlaunches the daemon (owns DB, event broadcaster, workflow engine)- CLI commands auto-start the daemon if not running (
DaemonClient::connect_or_start) - JSON-lines protocol over Unix socket for IPC
darq tuiconnects to the daemon for real-time event streaming
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.
- 4d ago First seen · 120 lines · 1,461 tokens per session scan A 89504a3cefb2
darq CLAUDE.md is an instructions file published in the GitHub repository dark-builders/darq (10 stars, last pushed 4mo ago), licensed MIT. It adds 1,461 tokens to every session, about $0.0073 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 instructions, from other repositories
revdiff CLAUDE.md
Claude Code instructions for umputun/revdiff, covering revdiff, commands, project structure, architecture principles and config.
cctop AGENTS.md
AGENTS.md instructions for st0012/cctop, covering agents.md - development guide for cctop, scope and sources, required development rules, driver workflow and github and pr rules.
toh-framework CLAUDE.md
Claude Code instructions for wasintoh/toh-framework, covering claude.md — toh framework (repo development guide), what this is, everyday commands, verification protocol and single source, transformed per ide.
examples CLAUDE.md
Claude Code instructions for rossoctl/examples, covering claude.md - agent examples, repository structure, key commands, code style and dco sign-off (mandatory).
agent-rules child-process.instructions.md
Instructions for lirantal/agent-rules, covering system processes secure coding guidelines, your mission and spawning system processes.
claude-code-templates CLAUDE.md
Claude Code instructions for Justdvp/claude-code-templates, covering claude.md, project overview, development commands, package management and application commands.