Borrowing it
Nothing to install: this file belongs to Smart-AI-Memory/attune-ai. 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/Smart-AI-Memory/attune-ai/main/.agents/skills/dev/SKILL.mdgit 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/skills/smart-ai-memory/attune-ai/dev)<a href="https://agentmods.dev/skills/smart-ai-memory/attune-ai/dev"><img src="https://agentmods.dev/badge/skills/smart-ai-memory/attune-ai/dev/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/skills/smart-ai-memory/attune-ai/dev"><img src="https://agentmods.dev/badge/skills/smart-ai-memory/attune-ai/dev.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00013 | $0.00896 |
| Opus 5.5 | $0.00005 | $0.00358 |
| Sonnet 5.5 | $0.00003 | $0.00179 |
| Haiku 4.5 | $0.00001 | $0.00090 |
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 1mo 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dev
Developer tools for daily coding workflows.
Routes
| Subcommand | Action |
|---|---|
review |
Code review workflow |
debug |
Debugging session |
refactor |
Refactoring session |
commit |
Stage and commit changes |
pr |
Create a pull request |
quality |
Code quality check |
perf-audit |
Performance audit |
Usage
/dev # Ask what to do
/dev review # Code review
/dev commit # Stage and commit
/dev debug # Debug session
/dev refactor # Refactoring
/dev pr # Create PR
Fast-Path Detection
When explicit args satisfy scoping, skip questions:
/dev commit --auto→ stage all + commit/dev review ./src/auth→ review that path/dev commit→ ask what to stage/dev→ ask what to do
Rule: If input contains BOTH an action AND a
target (or --auto flag), proceed to execution.
If either is missing, use AskUserQuestion.
Behavior
Plan Detection (all routes)
Before starting scoping questions for any route,
check for saved plans from /plan:
- Use
Globto check.claude/plans/{route}-*.mdfor the current route (e.g.,refactor-*.mdfor/dev refactor) - If matching plans exist, use
Readto check their Status field (skipcompletedplans) - If no pending plans match, proceed normally with the scoping flow below
- If multiple pending plans match, show a list and let the user choose which one
- If a pending/in-progress plan is found, use
AskUserQuestionwith these options:
- "Yes, use this plan": Read the plan file.
Update its Status to
in-progress. Use the plan's Scope and Approach sections to drive execution. Do NOT re-ask scoping questions. - "No, start fresh": Proceed with the normal
AskUserQuestionscoping flow below.
Example prompt:
question: "I found a saved plan:
{plan-title} ({date}). Pick up where you
left off?"
header: "Plan"
options:
- label: "Yes, use this plan"
description: "Skip scoping — execute based
on the saved plan"
- label: "No, start fresh"
description: "Ignore the plan and scope
from scratch"
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.
- 1mo ago First seen · 161 lines · 13 tokens per session scan A c9b1bf754729
dev is a skill published in the GitHub repository Smart-AI-Memory/attune-ai (10 stars, last pushed today), licensed Apache-2.0. It adds 13 tokens to every session and 896 once invoked, about $0.0001 per session on Opus 5.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
guardian
Gatekeeping Git/PR by classifying change essence and recommending granularity, naming, and strategy; the ship recipe also executes PR delivery (create, CI watch, merge, cleanup) with Ask First on merge. Use when PR preparation, commit strategy, or gated PR delivery is needed.
pr-authoring
Playbook for deployment-aware pull requests — the 11-section format that turns a PR into a reviewable contract; why, decision requested, change map, review order, evidence, verification, risk, rollback. Used for the Define→build handoff and any PR a great-pm-driven project opens.
pr-review
Playbook for reviewing pull requests — verdict format, verification-not-trust, severity-ranked findings with concrete fixes, risk acceptance on the record. The reviewer-side counterpart of pr-authoring.
feature-publish
Commit the feature, write the PR body, publish in the selected mode, and drive the PR.
lean-review
CocoLean diff-scoped over-engineering audit — scans uncommitted git diff and applies five classification tags (delete/stdlib/native/yagni/shrink) to identify unnecessary surface area before commit.
flag-cleanup
Weekly reusable-session feature-flag cleanup for {{targetrepo}}. Inventories every feature flag, classifies each as fully rolled out, long dead, partial rollout, or active experiment, removes the flag and the dead branch it guards on an isolated branch when the suite is green, and opens a PR — never touching a flag…