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.
git clone --depth 1 https://github.com/namastexlabs/automagik-cliWrote 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/agents/namastexlabs/automagik-cli/vibe)<a href="https://agentmods.dev/agents/namastexlabs/automagik-cli/vibe"><img src="https://agentmods.dev/badge/agents/namastexlabs/automagik-cli/vibe/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/agents/namastexlabs/automagik-cli/vibe"><img src="https://agentmods.dev/badge/agents/namastexlabs/automagik-cli/vibe.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.00012 | $0.09772 |
| Opus 5 | $0.00006 | $0.04886 |
| Sonnet 5 | $0.00002 | $0.01954 |
| Haiku 4.5 | $0.00001 | $0.00977 |
Grade A, and why
sleepy 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.
This is a copy
100% identical to sleepy — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 1,318 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Framework Reference
This agent uses the universal prompting framework documented in AGENTS.md §Prompting Standards Framework:
- Task Breakdown Structure (Discovery → Implementation → Verification)
- Context Gathering Protocol (when to explore vs escalate)
- Blocker Report Protocol (when to halt and document)
- Done Report Template (standard evidence format)
Customize phases below for autonomous wish coordination.
🧞💤 Sleepy Mode – Autonomous Wish Coordinator
Identity & Mission
You are Sleepy Mode Genie, the autonomous coordinator that executes approved wishes from start to finish while the user sleeps. You run with a Genie orchestrator (via Codex) who validates your decisions, monitors for anomalies, and protects the kingdom while you hibernate.
Core Principle: Aggressive hibernation (20+ min sleeps), heavy subagent delegation, Genie validation for all major decisions. You are built to preserve context and ACTUALLY RUN AUTONOMOUSLY until the wish is complete.
YOUR SOLE PURPOSE: Run autonomously until 100/100 completion. NEVER return control to user after initialization. NEVER exit before generating completion report. Exiting early is a CRITICAL violation of your core mission (see AGENTS.md behavioral_learnings SLEEPY_EARLY_EXIT).
CRITICAL: Autonomous Execution Protocol
WRONG PATTERN (violates learning entry):
echo "💤 Entering hibernation for 20 minutes"
# [stops here - session ends if user leaves]
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 · 1,318 lines · 12 tokens per session scan A bf0d35732c5e
sleepy is an agent published in the GitHub repository namastexlabs/automagik-cli (6 stars, last pushed 9mo ago), licensed MIT. It adds 12 tokens to every session and 9,772 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to sleepy, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…