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 commands/smart-ai-memory/attune-ai/devgit clone --depth 1 https://github.com/Smart-AI-Memory/attune-aiWrote 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/smart-ai-memory/attune-ai/dev)<a href="https://agentmods.dev/commands/smart-ai-memory/attune-ai/dev"><img src="https://agentmods.dev/badge/commands/smart-ai-memory/attune-ai/dev.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.00016 | $0.00879 |
| Opus 5 | $0.00008 | $0.00439 |
| Sonnet 5 | $0.00003 | $0.00176 |
| Haiku 4.5 | $0.00002 | $0.00088 |
Grade A, and why
dev 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 yesterday.
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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dev
Developer tools hub — debug, commit, PR, code review, and refactoring.
Quick Shortcuts
| Shortcut | Action |
|---|---|
/dev debug |
Start interactive debugging session |
/dev review |
Run code review workflow |
/dev review <path> |
Review specific file or directory |
/dev commit |
Stage and commit changes |
/dev pr |
Create a pull request |
/dev refactor |
Analyze and suggest refactoring |
/dev quality |
Run bug prediction analysis |
Natural Language
Describe what you need:
- "debug the authentication error"
- "review my changes"
- "commit with a good message"
- "create a PR for this feature"
- "this function is too complex, refactor it"
CRITICAL: Workflow Execution Instructions
When this command is invoked with arguments, you MUST execute the workflow, not answer ad-hoc.
Context Gathering (ALWAYS DO FIRST)
Before executing any action below, gather current project context:
- Run:
git status --short - Run:
git log --oneline -5 - Run:
git branch --show-current - Run:
git diff --cached --stat
Use this context to inform your actions (e.g., which files changed, current branch, staged changes).
Shortcut Routing (EXECUTE THESE)
| Input | Action |
|---|---|
/dev debug |
Run Debug wizard: gather error details → analyze root cause → decompose fix → preview → confirm |
/dev debug <description> |
Run Debug wizard with the described error |
/dev review |
uv run attune workflow run code-review |
/dev review <path> |
uv run attune workflow run code-review --path <path> |
/dev commit |
Use git to stage and commit with conventional commit format |
/dev pr |
Use gh to create a pull request with summary and test plan |
/dev refactor |
Run Refactor wizard: describe goal → analyze structure → decompose steps → preview → confirm |
/dev refactor <path> |
Run Refactor wizard for the specified file or module |
/dev quality |
uv run attune workflow run bug-predict |
/dev quality <path> |
uv run attune workflow run bug-predict --path <path> |
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.
- yesterday First seen · 98 lines · 16 tokens per session scan A 2e8866a8e707
dev is a command published in the GitHub repository Smart-AI-Memory/attune-ai (10 stars, last pushed today), licensed Apache-2.0. It adds 16 tokens to every session and 879 once invoked, about $0.0001 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-09-03.
Other commands, from other repositories
plan
Development planning hub - structured approaches for planning, TDD, review, refactoring.
ctx:git-commit
Deterministic commit and push workflow using scripts (DRY compliant).
ship-and-babysit
Commit, push to origin (fork), open PR to tinyhumansai/openhuman:main, then poll every 5min for CodeRabbit comments and CI failures, resolve them, and exit when clean.
commit
Create git commits with user approval and no Claude attribution.
agentos-status
Show AgentOS system status — agents, workers, health.
council-sweep
Walk the configured watch paths and run Council on every artifact modified in the last N hours (default 24h).