Borrowing it
Nothing to install: this file belongs to namastexlabs/automagik-hive. 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/namastexlabs/automagik-hive/main/.claude/commands/prompt.mdgit clone --depth 1 https://github.com/namastexlabs/automagik-hiveWrote 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/commands/namastexlabs/automagik-hive/prompt)<a href="https://agentmods.dev/commands/namastexlabs/automagik-hive/prompt"><img src="https://agentmods.dev/badge/commands/namastexlabs/automagik-hive/prompt/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/commands/namastexlabs/automagik-hive/prompt"><img src="https://agentmods.dev/badge/commands/namastexlabs/automagik-hive/prompt.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.00000 | $0.09635 |
| Opus 5.5 | $0.00000 | $0.03854 |
| Sonnet 5.5 | $0.00000 | $0.01927 |
| Haiku 4.5 | $0.00000 | $0.00963 |
Grade A, and why
prompt 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 2mo 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 — 643 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Advanced Prompting Framework
Task Decomposition Pattern
Break complex tasks into trackable subtasks for clarity and progress monitoring:
<task_breakdown>
1. [Discovery] What to investigate
- Identify affected components
- Map dependencies
- Document current state
2. [Implementation] What to change
- Specific modifications
- Order of operations
- Rollback points
3. [Verification] What to validate
- Success criteria
- Test coverage
- Performance metrics
</task_breakdown>
This pattern ensures systematic execution and allows agents to track progress through complex multi-step operations.
Auto-Context Loading with @ Pattern
Use @ symbols to automatically trigger file reading, eliminating manual context gathering:
[TASK]
Update authentication system
@src/auth/middleware.ts
@src/auth/config.json
@tests/auth.test.ts
Benefits:
- Agents automatically read files before starting
- No need for "first read X, then Y" instructions
- Ensures complete context from the start
- Reduces tool calls and latency
Example usage:
[CONTEXT]
Files to update:
@src/mastra/index.ts - Main configuration
@src/mastra/agents/*.ts - All agent files
Changes needed: Use consistent DB paths
Success/Failure Boundaries
Use visual markers to clearly define completion criteria and restrictions:
[SUCCESS CRITERIA]
✅ All tests pass
✅ No hardcoded paths
✅ Environment variables used consistently
✅ Memory properly initialized
✅ No console.log statements in production
[NEVER DO]
❌ Skip test coverage
❌ Commit API keys or secrets
❌ Use absolute file paths
❌ Leave TODO comments
❌ Accept partial completion as done
This pattern provides:
- Clear visual scanning of requirements
- Unambiguous completion criteria
- Explicit anti-patterns to avoid
- Reduced ambiguity in task interpretation
Concrete Examples Over Descriptions
Replace vague instructions with actual code snippets and specific patterns:
INSTEAD OF:
"Ensure proper error handling and logging"
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.
- 2mo ago First seen · 643 lines · 0 tokens per session scan A 3db4ee3faab3
prompt is a command published in the GitHub repository namastexlabs/automagik-hive (24 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 9,635 tokens. 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 commands, from other repositories
os-watcher
A command for turning reminders and end-of-session blocking on or off when a background watcher is not armed.
os-help
A command that displays the available AI Team OS slash commands and explains what each one does. Slash commands are short commands beginning with `/` that trigger specific actions.
os-status
A command for viewing the current state of an AI Team OS project, including teams, agents, and active meetings.
os-up
A command that checks and starts the AI Team OS API server and dashboard. An API server provides data and operations to other programs, while a dashboard is a web interface for viewing and using the system.
os-meeting
A command for listing active AI Team OS meetings, creating a meeting, or viewing a meeting’s messages and details.
agentos-status
Show AgentOS system status — agents, workers, health.