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/xsovad06/sova/claude-mdgit clone --depth 1 https://github.com/xsovad06/sovaWhat 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.01053 | $0.01053 |
| Opus 5 | $0.00526 | $0.00526 |
| Sonnet 5 | $0.00211 | $0.00211 |
| Haiku 4.5 | $0.00105 | $0.00105 |
Grade A, and why
sova 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 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@AGENTS.md
CLAUDE.md
This file provides Claude Code-specific commands and behaviors. Architecture, conventions, and cross-cutting rules are in AGENTS.md and .claude/rules/*.md -- this file contains only run commands, knowledge system config, and Claude-specific preferences.
Running the Project
# SOVA CLI (globally installed via: pip install --user --break-system-packages -e .)
sova --help # Show all commands
sova install /path/to/project # Install SOVA into a project
sova setup /path/to/project # Run setup wizard
sova uninstall /path/to/project # Remove SOVA from a project
sova run 42 # Work on issue #42
sova triage 42 # Triage a single issue
sova briefing # Show awareness briefing
sova dashboard --project /path # Start web UI at http://localhost:8111
# Server management (dashboard + scheduler daemon)
sova server start # Start the server
sova server restart # Restart the server
sova server stop # Stop the server
sova server status # Check if server is running
sova server digest --hours 24 # Show activity summary
sova server install-service --type systemd # Install as system service
# Dashboard (shortcut)
make serve # Start web UI at http://localhost:8111
# Development
make check # Run all linters + tests (CI-equivalent)
make test # Run bash + python tests
make lint # ShellCheck + Ruff
make format # Auto-format Python code
# Git hooks (after fresh clone)
git config core.hooksPath .githooks
Starting a Session
# Verify you are authenticated as the correct GitHub user (must match github_user in sova.toml)
gh auth status
Ticket workflow (branch naming, PR linking, etc.) is in AGENTS.md under "Development Workflow".
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 First seen · 132 lines · 1,053 tokens per session scan A 6a2e251972d2
sova CLAUDE.md is an instructions file published in the GitHub repository xsovad06/sova (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 1,053 tokens to every session, about $0.0053 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
KARIMO CLAUDE.md
Instructions for opensesh/KARIMO, covering karimo source repository rules, release protocol (mandatory), preferred method: release script, manual release checklist (if not using script) and critical: never move tags after release.
autonomous-dev CLAUDE.md
Claude Code instructions for akaszubski/autonomous-dev, covering autonomous-dev, critical rules, maintainer escape hatches, architecture and code navigation.
dark-factory CLAUDE.md
Claude Code instructions for peter-stratton/dark-factory, covering claude.md and where to look.
just-ship CLAUDE.md
Claude Code instructions for yves-s/just-ship, covering claude.md — just-ship, identity, decision authority, what just ship is and how work flows.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.