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 itsribbZ/Godspeed --skill toke-initgit clone --depth 1 https://github.com/itsribbZ/GodspeedWrote 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/itsribbz/godspeed/toke-init)<a href="https://agentmods.dev/skills/itsribbz/godspeed/toke-init"><img src="https://agentmods.dev/badge/skills/itsribbz/godspeed/toke-init.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.00047 | $0.01151 |
| Opus 5 | $0.00023 | $0.00575 |
| Sonnet 5 | $0.00009 | $0.00230 |
| Haiku 4.5 | $0.00005 | $0.00115 |
Grade B, and why
toke-init scanned grade B 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 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
TICK=$(cat ~/.claude/telemetry/brain/godspeed_count.txt 2>/dev/null || echo 0) How it starts
The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Toke Init — Session Pre-Flight
Invoke at session start to load Toke context and verify system health.
Project Paths
| Item | Path |
|---|---|
| Toke root | $TOKE_ROOT (set via env var; defaults to the cloned repo location) |
| Project status | ~/.claude/projects/<current-slug>/memory/project_status.md |
| Memory index | ~/.claude/projects/<current-slug>/memory/MEMORY.md |
| Global settings | ~/.claude/settings.json |
| Installed skills | ~/.claude/skills/ |
| Slash commands | ~/.claude/commands/ |
Phase 1: Load (parallel)
Read these in one parallel batch so nothing blocks:
- Project status —
~/.claude/projects/<current-slug>/memory/project_status.md(if exists) — where we left off - Memory index —
~/.claude/projects/<current-slug>/memory/MEMORY.md(if exists) — pointer list - Toke README —
$TOKE_ROOT/README.md— big-picture refresher (optional — skip if already loaded)
If a file is missing → warn but continue. Never block init on a missing file.
Phase 2: Health Check (fast, ≤ 5 seconds)
Parallel shell block — catches broken pipelines early:
# Brain telemetry
DECISIONS=$(wc -l < ~/.claude/telemetry/brain/decisions.jsonl 2>/dev/null || echo 0)
TOOLS=$(wc -l < ~/.claude/telemetry/brain/tools.jsonl 2>/dev/null || echo 0)
TICK=$(cat ~/.claude/telemetry/brain/godspeed_count.txt 2>/dev/null || echo 0)
echo "Brain: ${DECISIONS} decisions, ${TOOLS} tool calls, tick ${TICK}"
# Homer pantheon
python $TOKE_ROOT/automations/homer/homer_cli.py status 2>&1 | head -12
# Mnemos store
python $TOKE_ROOT/automations/homer/mnemos/mnemos.py health 2>&1 | head -12
# Zeus CLI
python $TOKE_ROOT/automations/homer/zeus/zeus_cli.py status 2>&1 | tail -5
Report inline. Flag any layer that fails its health check. Do NOT block init on a health warning — surface it in the briefing.
Phase 3: Briefing
Render a one-screen summary — real data from Phase 1+2, no placeholders:
═══════════════════════════════════════
TOKE — SESSION READY
═══════════════════════════════════════
LAST SESSION: [date from project_status.md] — [one-line summary]
Completed: [bullets from status]
In-Progress:[bullets from status]
Next Up: [bullets from status]
TOKE SYSTEMS:
Brain: [N] decisions logged, tick [N]
Homer: [N]/8 layers live, [N]/[N] integration tests green
Mnemos: [N] recall rows, semantic_available=[T/F]
Zeus: atomic gate-write CLI [OK/missing]
READY. What are we building?
═══════════════════════════════════════
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 · 115 lines · 47 tokens per session scan B ef1aaefd34bf
toke-init is a skill published in the GitHub repository itsribbZ/Godspeed (1 stars, last pushed 2mo ago), licensed MIT. It adds 47 tokens to every session and 1,151 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
ccc-resume-session
Load the last saved session file from /.claude/sessions/ and orient fully before doing any work. Reads the complete file, formats a structured briefing (project,…
scout-consolidation
Launch a Scout consolidation session as a background process. Runs a lighter delta scan — captures what changed since the last run and updates action items and KB.
maude
Use when the user is starting a session, losing track of where something is, asking "where did I put X", "where is X", "what's the state of Y", "what changed", wants to audit their config or setup, says "save this", "remember this", "remind me about Z", or invokes any /maude: command. ALSO use when the user expresses…
g-resume
Re-hydrate a fresh session with the right slice of the durable record. The read-side counterpart to /g-retro — selectively retrieves the relevant retro, ADRs, journal, and handoff keyed by the current branch/milestone/first-task, and assembles a focused re-entry briefing. Loads distilled context into a clean window…
daily-briefing
Proactive daily briefing that fires on a recurring schedule, pulls recent memory and workspace context, composes a structured summary (action items, progress, radar, next steps), and delivers it to all active channels. Enable with a time like "set up my daily briefing at 9am". Disable, reschedule, or check status at…
agentic-os-obsidian
Set up an agentic OS inside an Obsidian vault — a configurable command-center dashboard with 5 auto-installed, bundled plugins (Dataview, CustomJS, Shell-commands, Terminal, Homepage), Home + per-profile + Vault Overview pages, KPI cards, sparklines, heatmap, task rollup, and a button bar wired to user-defined Claude…