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/dakera-ai/dakera-cli/claude-mdgit clone --depth 1 https://github.com/Dakera-AI/dakera-cliWhat 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.00282 | $0.00282 |
| Opus 5 | $0.00141 | $0.00141 |
| Sonnet 5 | $0.00056 | $0.00056 |
| Haiku 4.5 | $0.00028 | $0.00028 |
Grade A, and why
dakera-cli 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 3d 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.
What it actually says
dakera-cli
Rust CLI for the Dakera AI memory platform — manage memories, sessions, agents, namespaces, keys, and vector search from the command line.
Key Commands
cargo build --release # Build CLI binary → target/release/dakera-cli
cargo test # Run tests
cargo clippy # Lint
cargo fmt # Format
./target/release/dakera-cli --help # Show all subcommands
Architecture
src/main.rs— CLI entry; clap command routingsrc/commands/— One module per subcommand: memory, session, agent, keys, knowledge, vector, namespace, admin, health, ops, analytics, completion, init, config, indexsrc/config.rs— Reads ~/.dakera/config.toml (API base URL + auth token)src/output.rs— Table / JSON / pretty-print output formatterssrc/error.rs— Error types wrapping API responses
Conventions
- Commands map 1-to-1 to dakera REST API endpoints
- Default output: human-readable table;
--jsonflag for machine-parseable output - Config precedence: env vars > CLI flags > ~/.dakera/config.toml
- Releases published alongside the dakera server (same version tag)
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.
- 3d ago First seen · 28 lines · 282 tokens per session scan A 4869369eeee5
dakera-cli CLAUDE.md is an instructions file published in the GitHub repository Dakera-AI/dakera-cli (8 stars, last pushed 17d ago), licensed MIT. It adds 282 tokens to every session, about $0.0014 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
dakera-rs CLAUDE.md
Claude Code instructions for Dakera-AI/dakera-rs, covering dakera-rs, key commands, architecture and conventions.
shodh-memory CLAUDE.md
Instructions for varun29ankuS/shodh-memory, covering shodh-memory project instructions, must rules, code standards, persistent memory (shodh-memory mcp) and codebase map.
vellis AGENTS.md
Instructions for volantlabs/vellis, covering agents.md, repository purpose, startup checks, installing vellis for a user and model-first component workflow.
pos CLAUDE.md
Instructions for xcota/pos, covering personal os, rules, memory, budget and hard rules.
pos AGENTS.md
Instructions for xcota/pos, covering agents.md — workspace boot rules, session boot, memory, safety and language.
cli AGENTS.md
Instructions for konteks/cli, covering agent instructions, project overview, tech stack, repository layout and common commands.