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 Smart-AI-Memory/attune-ai --skill lookup-warngit 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/lookup-warn)<a href="https://agentmods.dev/skills/smart-ai-memory/attune-ai/lookup-warn"><img src="https://agentmods.dev/badge/skills/smart-ai-memory/attune-ai/lookup-warn/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/lookup-warn"><img src="https://agentmods.dev/badge/skills/smart-ai-memory/attune-ai/lookup-warn.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 34 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00051 | $0.00462 |
| Opus 5.5 | $0.00020 | $0.00185 |
| Sonnet 5.5 | $0.00010 | $0.00092 |
| Haiku 4.5 | $0.00005 | $0.00046 |
Grade A, and why
lookup-warn 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.
What it actually says
Lookup Warn
File-context warnings for the file the user is editing or
about to edit. Uses the lookup_warn MCP tool, which maps
the file extension and name to relevant tags and returns
the top N matching warning and task templates.
When to use
- User is about to edit a file and wants to know the pitfalls
- User asks "what should I watch out for" on a specific file
- IDE selection changed — proactively surface warnings
Scoping
If no file path is provided, use AskUserQuestion:
question: "Which file should I check?"
header: "lookup-warn"
options:
- label: "The file I'm currently viewing"
description: "Use the IDE selection (if one is active)"
- label: "A different file"
description: "Provide a path relative to the project root"
If an IDE selection is available, prefer it without asking.
Execution
- Call the MCP tool
lookup_warnwith:file_path— the user's filemax_results— 3 by default, or what the user asked fortemplate_dir—.help/templatesif the project has one, otherwise omit
- If
countis 0, tell the user there are no known warnings for this file type and suggest runninglookup-listto browse topics manually. - Print each entry in the
warningsarray as a list item.
Output Format
## Warnings for `<file-path>`
3 relevant topics:
1. <first warning content>
2. <second warning content>
3. <third warning content>
*To look up any of these topics in more detail, say 'look up X'.*
Keep entries compact — the templates are already rendered. Don't paraphrase the tool output.
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 · 66 lines · 51 tokens per session scan A 9c7bce66f9ee
lookup-warn is a skill published in the GitHub repository Smart-AI-Memory/attune-ai (10 stars, last pushed yesterday), licensed Apache-2.0. It adds 51 tokens to every session and 462 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
ripple
Analyzing pre-change impact across vertical (dependency chains, files) and horizontal (pattern consistency, naming) dimensions. Use to estimate blast radius before a refactor. No code.
tome
Converting technical knowledge into durable learning documents and publishable articles. Use for diff-based teaching, decision records, onboarding, note/Zenn/Qiita/dev.to posts, article series, retrospectives, and cross-platform repurposing.
sweep
Detecting unnecessary files, unused code, and orphaned files, and proposing safe deletion. Not for removal execution (Builder), repo structure (Grove), or scope cutting (Void).
bolt
Optimizing frontend (re-render, memoization, lazy loading) and backend (N+1, indexing, caching, async) performance, plus continuous auto-tuning loops for GC/threadpool/cache/worker settings.
lens
Comprehending and investigating codebases: structure mapping, feature discovery, data flow tracing for 'does X exist?' or 'how does Y work?'. Includes a conversational ask mode. Does not write code.
scout
Investigating bugs via root cause analysis, reproduction steps, and impact assessment. Investigation-only — finds why bugs occur and where to fix them, no code. Use when a bug needs RCA before a fix.