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 carmelyne/inkobytes-nexus --skill nexusgit clone --depth 1 https://github.com/carmelyne/inkobytes-nexusWrote 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/carmelyne/inkobytes-nexus/nexus)<a href="https://agentmods.dev/skills/carmelyne/inkobytes-nexus/nexus"><img src="https://agentmods.dev/badge/skills/carmelyne/inkobytes-nexus/nexus/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/carmelyne/inkobytes-nexus/nexus"><img src="https://agentmods.dev/badge/skills/carmelyne/inkobytes-nexus/nexus.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.00064 | $0.01381 |
| Opus 5 | $0.00032 | $0.00691 |
| Sonnet 5 | $0.00013 | $0.00276 |
| Haiku 4.5 | $0.00006 | $0.00138 |
Grade A, and why
nexus 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nexus
Nexus CLI is the coordination engine. This skill is only the agent playbook.
If the user, repo, or hook says Nexus is active, treat this skill as mandatory workflow. It is not optional advice.
Loop
-
Run
nexus start; setNEXUS_AGENTfor your CLI, or pass--agent @agy|@claude|@codex|@gemini. Start is orientation only, not permission to edit. -
Read
_NEXUS_CONSTITUTION.md. -
Read
USER.mdif present for local user preferences. -
Read continuity and latest memory at session start,
nexus start, or resume. -
Read
_NEXUS_QUEUE.mdand_NEXUS_STANDUP.md. -
Choose user-assigned work or
nexus next @Agent; do not free-roam intoAuto-flow: no. -
Claim exact shared files before editing, and before reading shared non-orientation files:
nexus claim <path> @Agent "intent" -
Compare the claim freshness receipt with your last read: same blob hash means your cached read is current; different or unknown means re-read before editing. Use
nexus claim --showfor the full file dump. -
If a hook blocks access because a shared path is unclaimed, stop and claim that exact path. Do not work around the hook with another command, cached content, or manual git operation.
-
Work only inside the claimed surface and run focused validation.
-
Release each claimed tracked file through Nexus as soon as it reaches a coherent checkpoint:
nexus release <path> "short commit message"
- Do not hold claims to bundle related work into a prettier feature commit. Nexus is agent-native and file-native: optimize for file availability, rollback safety, and agent throughput.
Queue Items
When adding work to _NEXUS_QUEUE.md, keep tasks dashboard-parseable and immediately actionable. Use this shape:
- [ ] TASK/@agent: Short task title
- Id: stable-kebab-id
- Epic: Product area or safety theme
- Status: Ready
- Depends on: none
- Files: path/one.js, path/two.md
- Affinity: cli, docs, dashboard
- Cost: small
- Auto-flow: yes
- Review: approved
- Approved by: human
- Notes: One practical paragraph with scope, constraints, and definition of done.
- Goal: Why this task exists, one line.
- Outcome: What must be true when the task is complete.
- Constraints: What the agent must not change or assume.
- Stop If: Conditions that require stopping for human review.
- Evidence: Tests, logs, or reports that prove completion.
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 · 92 lines · 64 tokens per session scan A 563b3094129b
nexus is a skill published in the GitHub repository carmelyne/inkobytes-nexus (5 stars, last pushed 2mo ago), licensed MIT. It adds 64 tokens to every session and 1,381 once invoked, about $0.0003 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
dos-dispatch-loop
Run recurring dos-dispatch cycles, switching to dos-replan when the backlog drains and stopping on the kernel's loop verdict. Use for unattended dispatch->replan->dispatch work across disjoint lanes.
dos-goal-fleet
Launch multiple goal-scoped workers in waves, each with a witness-gated stop condition and dos arbitrate file-tree safety. Use when an operator asks to run several independent goals in parallel and fold only verified ships.
dos-next-up
Snapshot the repo's phased-plan portfolio into a dispatch packet: audit candidates with dos verify, render who-does-what, and emit a dos gate verdict. Use when you need the current next-work view before dispatching agents.
dos-dispatch
Plan and ship the next batch on one lane: run dos-next-up, acquire a lease with dos arbitrate, gate empty work, dispatch the packet, and archive the run. Use when a single lane should move end to end with collision safety.
dos-replan
Refresh a plan portfolio from evidence: close shipped queue items, update cooldown state, and surface the few decisions an operator must make. Use after dispatch bursts, drained backlogs, or recurring findings.
squads-cli
Squads CLI — operate your AI workforce through the loop; intent in, reviewed work out. TRIGGER when running squads, dispatching agents, triaging the inbox, reading/writing memory, recording feedback, or checking status/usage.