Borrowing it
Nothing to install: this file belongs to enowdev/succubus. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/enowdev/succubus/main/.agents/skills/succubus/SKILL.mdgit clone --depth 1 https://github.com/enowdev/succubusWrote 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/enowdev/succubus/succubus)<a href="https://agentmods.dev/skills/enowdev/succubus/succubus"><img src="https://agentmods.dev/badge/skills/enowdev/succubus/succubus/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/enowdev/succubus/succubus"><img src="https://agentmods.dev/badge/skills/enowdev/succubus/succubus.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.00062 | $0.00923 |
| Opus 5.5 | $0.00025 | $0.00369 |
| Sonnet 5.5 | $0.00012 | $0.00185 |
| Haiku 4.5 | $0.00006 | $0.00092 |
Grade A, and why
succubus 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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- succubus — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
succubus — working alongside other agents
Several AI agents may be working in this repository right now. succubus is the shared record of who is here, what the plan is, which tasks are taken, and which files are locked.
Do this first
Call succubus_register. It returns the name you are known by here — for
example ORION. That name is your identity in this project: use it when
referring to yourself, and when other agents refer to you.
The response also contains the current state: the active plan, your tasks, the other agents present, and the files they hold. Read it before you plan anything.
If you have forgotten your name — after a long session, or a context
compaction — call succubus_whoami.
Before you edit any file
Call succubus_claim_files with the paths you are about to change.
- Granted — go ahead. Call
succubus_release_fileswhen you are done. - Denied — another agent holds that file. Do not edit it. Work on
something else, or leave the holder a note with
succubus_handoff.
Claims expire on their own, so a crashed agent never blocks a file forever. You do not need to worry about cleaning up after someone else.
To check availability without taking a lock, use succubus_check_files.
Plan before you build
If there is no active plan and the work is not trivial, write one first with
succubus_plan_create — what you are building and the approach you intend to
take. Every agent reads the active plan on every turn, so this is the cheapest
way to keep four sessions pointed the same direction.
Keep it current with succubus_plan_update as the approach changes. A stale
plan is worse than none, because agents act on it.
Working on tasks
The board is only useful if it reflects what is happening now, so write to it as you work rather than afterwards.
succubus_task_create— record work as you identify it, before doing it. An unrecorded task is one another agent may start in parallel.succubus_task_list— check the board before inventing new work; the task may already exist.succubus_task_claim— take ownership so no one else starts the same thing.succubus_task_update—in_progresswhen you begin,reviewordonewhen you finish. Never leave a task inin_progressthat you have stopped working on: it tells every other agent a lie.
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.
- 1mo ago First seen · 87 lines · 62 tokens per session scan A 45e073a5902f
succubus is a skill published in the GitHub repository enowdev/succubus (17 stars, last pushed 3mo ago), licensed MIT. It adds 62 tokens to every session and 923 once invoked, about $0.0002 per session on Opus 5.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-30.
Other skills, from other repositories
github-multi-repo
Multi-repository coordination, synchronization, and architecture management with AI swarm orchestration.
self-optimize
Tune skill/guide/persona/model selection to the project for quality+cost; gabbe.config.json + autonomy levels + alignment.
paperclip
Use for Paperclip-managed tasks and heartbeats: reading task context, delivering task documents or files, updating completion or blockers, coordinating or delegating work, and following company governance. Includes control plane API operations for assignments, comments, approvals, and routines.
paperclip-task-bridge
Create, comment on, update, and list Paperclip tasks from Hermes using scoped Paperclip API credentials.
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.