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 skills add MohmmedAshraf/symbiote --skill symbiote-dnagit clone --depth 1 https://github.com/MohmmedAshraf/symbioteWrote 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/skills/mohmmedashraf/symbiote/symbiote-dna)<a href="https://agentmods.dev/skills/mohmmedashraf/symbiote/symbiote-dna"><img src="https://agentmods.dev/badge/skills/mohmmedashraf/symbiote/symbiote-dna/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/skills/mohmmedashraf/symbiote/symbiote-dna"><img src="https://agentmods.dev/badge/skills/mohmmedashraf/symbiote/symbiote-dna.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.00084 | $0.00668 |
| Opus 5 | $0.00042 | $0.00334 |
| Sonnet 5 | $0.00017 | $0.00134 |
| Haiku 4.5 | $0.00008 | $0.00067 |
Grade A, and why
symbiote-dna 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 12d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Symbiote Developer DNA
Manage developer coding preferences that Symbiote learns and enforces across sessions.
What is Developer DNA
DNA entries are coding rules Symbiote tracks with confidence scores. They have:
- rule — the specific coding preference
- reason — why it matters
- category — formatting, patterns, architecture, workflow, testing, tooling, ai-collaboration
- confidence — 0.0 to 1.0 (auto-promoted as patterns are observed)
- applies_to — language/framework scope
- source — explicit (user-stated), correction (from feedback), observed (from code patterns)
Commands
View Current DNA
Use the get_developer_dna MCP tool. Filter by category:
get_developer_dna({ category: "formatting" })
get_developer_dna({ category: "patterns" })
get_developer_dna({}) // all entries
Record a New Preference
Use the record_instruction MCP tool:
record_instruction({
rule: "Always use early returns over nested if-else",
reason: "Reduces cognitive load and keeps functions flat",
category: "patterns",
applies_to: ["typescript", "javascript"],
source: "explicit"
})
CLI Profile Management
npx -y symbiote-cli dna # Show active profile summary
npx -y symbiote-cli dna list # List all profiles
npx -y symbiote-cli dna switch # Switch active profile
npx -y symbiote-cli dna export # Export profile to .dna.json
npx -y symbiote-cli dna import # Import a shared profile
npx -y symbiote-cli dna diff # Compare two profiles
Export and Share
Export the current profile for team sharing:
npx -y symbiote-cli dna export
This creates a .dna.json file that teammates can import:
npx -y symbiote-cli dna import path/to/.dna.json
Compare Profiles
Diff two profiles to see divergence:
npx -y symbiote-cli dna diff
Output
When showing DNA, format as a clean grouped list:
## Developer DNA — {profile name}
### Formatting ({count})
- Use 4-space indentation everywhere (confidence: 1.0)
- Single quotes for strings (confidence: 0.9)
### Patterns ({count})
- Prefer early returns over nesting (confidence: 1.0)
- const over let, never var (confidence: 0.8)
### Architecture ({count})
- ...
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.
- 12d ago First seen · 98 lines · 84 tokens per session scan A 982e0047dfbb
symbiote-dna is a skill published in the GitHub repository MohmmedAshraf/symbiote (5 stars, last pushed 5mo ago), licensed MIT. It adds 84 tokens to every session and 668 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 skills, from other repositories
dekko-notes
Read and write dekko's symbol-anchored notes in any repo with a .dekko/ directory. Trigger every time you pull a symbol's context (querysymbol, getcontextpack, dekko query/context), right after a non-obvious change, and right after any rename/move/signature edit (to sweep orphaned notes). Notes are durable, committed…
roam
Codebase comprehension via roam-code CLI. Use when exploring codebases, planning modifications, debugging failures, assessing PR risk, or checking architecture health. Triggers on: understanding project structure, pre-change safety checks, finding symbols/files, blast radius analysis, affected tests, health scoring…
durable-session-state
Persist plans, scope decisions, evidence, and reviewer/critic verdicts to durable files during long or multi-phase tasks so work survives context compaction, session resumes, and handoffs. Use for swarm-mode tasks, before context grows large, when recording approval gates, and when resuming after compaction or a…
save-progress
Save current project task progress to local task state file for cross-session continuity. Use when the user asks to save progress, uses an equivalent localized trigger phrase, the session is interrupted, or the user wants to resume work later. Writes to .claude/project-task-state.json so next session can load it via…
memorix
Use when Claude Code needs Memorix shared memory, reasoning, Git Memory, mini-skills, session handoff, orchestration coordination, or integration troubleshooting.
memorix-mini-skills
Use when durable project knowledge, gotchas, workflows, or repeated fixes should become reusable agent guidance instead of ordinary memory.