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 mahmoudimus/simba --skill simba-onboardgit clone --depth 1 https://github.com/mahmoudimus/simbaWrote 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/mahmoudimus/simba/simba-onboard)<a href="https://agentmods.dev/skills/mahmoudimus/simba/simba-onboard"><img src="https://agentmods.dev/badge/skills/mahmoudimus/simba/simba-onboard.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.1 | $0.00071 | $0.00812 |
| Opus 5 | $0.00036 | $0.00406 |
| Sonnet 5 | $0.00014 | $0.00162 |
| Haiku 4.5 | $0.00007 | $0.00081 |
Grade A, and why
simba-onboard 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 6d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Simba Onboard
Set up SIMBA markers for a project by analyzing existing markdown files and generating consolidated core instructions.
Follow these steps in order.
Step 0: Resolve Core Filename
Run:
simba config get guardian.core_filename
Use the returned filename as ${CORE_FILE} for all following steps. Default is CORE_INSTRUCTIONS.md.
Step 1: Discover Existing Files
Collect onboarding inputs:
- Read
CLAUDE.mdif it exists. - Read
AGENTS.mdif it exists. - Read
.mdfiles under.claude/, excluding.claude/handoffs/and.claude/notes/. - Run
simba markers audit. - Run
simba markers list.
Report all files found, approximate sizes, and any existing markers or <!-- CORE --> tags.
Step 2: Analyze Content
Extract and categorize instructions from discovered files:
| Category | What to extract | SIMBA section |
|---|---|---|
| Critical Constraints | Non-negotiable rules and security requirements | constraints |
| Build & Test | Build/test commands and CI steps | build_commands |
| Environment | Paths, ports, machines, deployment targets | environment |
| Code Style | Formatting and naming conventions | code_style |
| Workflow | Git/PR conventions and process rules | workflow |
| Agent Rules | Agent/subagent dispatch and context rules | agent_rules |
Rules:
- Create only categories with real content.
- Preserve original wording where possible.
- Deduplicate repeated rules.
Report a table of category, source files, and item counts.
Step 3: Draft .claude/rules/${CORE_FILE}
Prepare a full draft with SIMBA markers:
- Use one marker pair per section:
<!-- BEGIN SIMBA:{name} -->and<!-- END SIMBA:{name} -->. - Keep
SIMBA:coretight and critical only. - Separate sections with
---.
SIMBA:core is re-injected repeatedly by guardian logic, so keep it concise.
Step 4: Ask for Verification Before Writing
Show the full proposed file first.
For each section include:
- Marker name.
- Proposed content.
- Source file(s).
- Explicit note for
SIMBA:corethat it is repeatedly re-injected.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 114 lines · 71 tokens per session scan A 1d9828f81d7e
simba-onboard is a skill published in the GitHub repository mahmoudimus/simba (6 stars, last pushed 1mo ago), licensed MIT. It adds 71 tokens to every session and 812 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
hivemind-goals
Create, track and update team goals + KPIs via the Deeplake virtual filesystem at memory/goal/ and memory/kpi/. Use whenever the user mentions a goal, objective, KPI, target, milestone, or asks to track progress on something measurable. ALSO use when the user says "task", "todo", "work item", "remind me to", "fix X"…
review-proposals
Triages pending improvement-proposal MCP items — presents each with its scope and evidence, collects an accept/reject/defer decision per proposal, and carries out the disposition: project-scoped acceptances get their exact YAML applied to .taskorchestrator/config.yaml and pushed per-root; global acceptances get a…
work-summary
Generates a project dashboard from MCP work items. Default is a lean, attention-first view: what's in flight, what's blocked, what to do next, what's queued. Use when the user says: project status, what's active, show me the dashboard, work summary, what should I work on, project health, what's blocked, where did I…
adopt-project-scope
Migrates an already-populated, unscoped Task Orchestrator database in place to the project-scoping convention — creates a project anchor root, re-parents existing work trees under it, and writes rootId back to config.yaml. Use when a user says: adopt project scope, migrate this database to project scoping, make this…
create-item
Creates an MCP work item from conversation context. Scans existing containers to anchor the item in the right place (Bugs, Features, Tech Debt, Observations, etc.), infers type and priority, creates single items or work trees, and pre-fills required notes. Use when the conversation surfaces a bug, feature idea, tech…
dependency-manager
Visualizes, creates, and diagnoses dependencies between MCP work items. Use when a user says: what blocks this, add a dependency, show dependency graph, why can't this start, link these items, unblock this, remove dependency, or show blockers.