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 agentmods add skills/bgill55/daedalus/add-slash-commandnpx skills add bgill55/daedalus --skill add-slash-commandgit clone --depth 1 https://github.com/bgill55/daedalusWrote 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/bgill55/daedalus/add-slash-command)<a href="https://agentmods.dev/skills/bgill55/daedalus/add-slash-command"><img src="https://agentmods.dev/badge/skills/bgill55/daedalus/add-slash-command.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 | $0.00032 | $0.00764 |
| Opus 5 | $0.00016 | $0.00382 |
| Sonnet 5 | $0.00006 | $0.00153 |
| Haiku 4.5 | $0.00003 | $0.00076 |
Grade A, and why
add-slash-command 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 5d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adding a Slash Command to Daedalus
Commands live in src/commands/ and are aggregated in src/commands/index.ts.
ESM only, named exports, .js extension on imports, no comments unless necessary.
Command shape
src/commands/types.ts defines Command:
export interface Command {
name: string; // '/spinner'
aliases?: string[]; // ['spin']
description: string;
usage?: string;
helpText?: string;
execute: (args: string, ctx: CommandContext) => Promise<boolean | void>;
}
Steps
- Create
src/commands/<name>.tsexportingexport const <name>Commands: Command[]. Insideexecute, usectx.config(typedDaedalusConfig),ctx.configDir,ctx.router. - To persist a config change, mirror
/config(src/commands/dev.ts ~line 964):
Validate input BEFORE mutating; reject unknown values with a friendly message.const { saveConfig, ConfigSchema } = await import('../config/index.js'); ctx.config.ui.spinner = arg; const validated = ConfigSchema.parse(ctx.config); ctx.config = validated; saveConfig(validated); if (ctx.router && typeof ctx.router.updateConfig === 'function') { ctx.router.updateConfig(ctx.config.router); } - Register in
src/commands/index.ts:import { <name>Commands } from './<name>.js';then spread...<name>Commands,intocommandsList. - CRITICAL — docs will break CI if you skip this.
src/docs.test.tshas two tests that fail unless the command is in BOTH the docs generator and the test's own copy:scripts/sync-docs.ts: add the command toCOMMAND_GROUPS(array) ANDCOMMAND_USAGES(map).src/docs.test.ts: add the SAME entries to its duplicateCOMMAND_GROUPS+COMMAND_USAGES.- Then run
npm run sync-docsto regenerate README.md + docs/configuration-reference.md. The usual failure: a missingCOMMAND_USAGESentry → test says "commands table is out of sync".
- Add
src/commands/<name>.test.ts. For config-persisting commands,vi.mock('../config/index.js')with{ ConfigSchema: { parse: (c) => c }, saveConfig: vi.fn() }so no real disk write; assertsaveConfigcalled andctx.router.updateConfigfired.
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.
- 5d ago First seen · 66 lines · 32 tokens per session scan A 155fcd8fd62c
add-slash-command is a skill published in the GitHub repository bgill55/daedalus (4 stars, last pushed 5d ago), licensed MIT. It adds 32 tokens to every session and 764 once invoked, about $0.0002 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
release
Release a new version of the project.
commit
Inspect git status, draft a commit message that matches the repo's style, and commit staged changes.
tlamatini-self-update-inclusion
Sweep the whole codebase and keep the SELF-UPDATE pipeline complete — so every new asset/feature added to Tlamatini is actually carried into a release by build.py AND survives (or is correctly replaced by) the self-update swap. Invoke whenever you add/rename a new agent, top-level file or directory, dependency…
tlamatini-self-modify-inclusion
Sweep the whole codebase and keep the SELF-MODIFY source snapshot complete — so the TlamatiniSourceCode/ tree that a --self-modify build ships carries every source/build asset Tlamatini needs to read, modify, and REBUILD herself, with heavy media/secrets correctly omitted+redacted and omitted binaries listed in the…
tlamatini-daily-chat-test
Run the daily automated Tlamatini chat regression — drive a visible Chrome via Playwright, log into agentpage.html, ask up to 1000 curated safe questions one-by-one (Multi-Turn ON, ACPX/Ask-Execs/Exec-Report/Internet OFF), wait for and qualify each answer (heuristic + LLM judge on failures), then write a dated report…
adding-external-mcp
The authoritative reference for adding a NEW external MCP server to Tlamatini universal MCP client layer. Covers the full lifecycle: catalog import, transport selection, activation, runtime provisioning, diagnosis, verification, and troubleshooting. READ THIS BEFORE calling externalmcpimport, before editing…