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-initgit 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-init)<a href="https://agentmods.dev/skills/mohmmedashraf/symbiote/symbiote-init"><img src="https://agentmods.dev/badge/skills/mohmmedashraf/symbiote/symbiote-init/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-init"><img src="https://agentmods.dev/badge/skills/mohmmedashraf/symbiote/symbiote-init.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.00087 | $0.01885 |
| Opus 5 | $0.00044 | $0.00942 |
| Sonnet 5 | $0.00017 | $0.00377 |
| Haiku 4.5 | $0.00009 | $0.00188 |
Grade A, and why
symbiote-init scanned grade A with 1 finding 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 11d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
sleep 3 && curl -s http://127.0.0.1:$(cat .brain/port)/internal/health How it starts
The opening of the file, as written. The whole thing — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Symbiote Project Init
Initialize Symbiote for the current project — scan codebase and extract DNA + intent.
MCP server is already registered globally by symbiote install. This skill only scans and extracts.
Process
- Scan the codebase and start the server
- Write project overview
- Scan ALL projects for developer identity
- Build complete DNA entries, constraints, and decisions
- Dispatch subagent with pre-built entries
- Print one-line summary
Step 1: Scan and Start Server
Run these as SEPARATE bash commands:
npx symbiote-cli scan
Then start the server:
npx symbiote-cli serve --no-open > /dev/null 2>&1 &
Then wait and verify:
sleep 3 && curl -s http://127.0.0.1:$(cat .brain/port)/internal/health
IMPORTANT: Do NOT combine scan and serve into one command. The scan must finish and release the DB lock before the server starts.
Step 2: Write Project Overview
Write .brain/intent/overview.md — a concise project summary that gives AI tools instant context.
Read the codebase context (CLAUDE.md, package.json, top-level structure, scan results) and write a markdown file with this exact structure:
# {Project Name}
{One sentence: what this project does and who it's for.}
## Tech Stack
- {Language/runtime} ({key detail})
- {Framework} ({purpose})
- {Database/storage} ({why chosen})
- {Other significant deps}
## Architecture
- `{top-level-dir}/` — {what it contains}
- `{top-level-dir}/` — {what it contains}
## Key Patterns
- {How data flows}
- {How modules connect}
## Entry Points
- `{file}` — {what it does}
Rules: keep it under 40 lines, no frontmatter, be specific to THIS project.
Step 3: Scan ALL Projects for Developer Identity
Read the developer's full coding identity across every project:
~/.claude/CLAUDE.md— global instructions- Every CLAUDE.md in
~/.claude/projects/*/— all project instructions - Every
.mdfile in~/.claude/projects/*/memory/— all memories ./CLAUDE.md— current project
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.
- 11d ago First seen · 222 lines · 87 tokens per session scan A dcbb4a7f7a60
symbiote-init is a skill published in the GitHub repository MohmmedAshraf/symbiote (5 stars, last pushed 5mo ago), licensed MIT. It adds 87 tokens to every session and 1,885 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.