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 axiomantic/spellbook --skill opportunity-awarenessgit clone --depth 1 https://github.com/axiomantic/spellbookWrote 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/axiomantic/spellbook/opportunity-awareness)<a href="https://agentmods.dev/skills/axiomantic/spellbook/opportunity-awareness"><img src="https://agentmods.dev/badge/skills/axiomantic/spellbook/opportunity-awareness/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/axiomantic/spellbook/opportunity-awareness"><img src="https://agentmods.dev/badge/skills/axiomantic/spellbook/opportunity-awareness.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.00038 | $0.00487 |
| Opus 5.5 | $0.00015 | $0.00195 |
| Sonnet 5.5 | $0.00008 | $0.00097 |
| Haiku 4.5 | $0.00004 | $0.00049 |
Grade A, and why
opportunity-awareness 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Opportunity Awareness
Type: Discipline (behavioral nudge)
Invariant Principles
- Pause Points Only - Surface observations after phases complete or at "what's next" moments, never mid-task or during urgent work.
- Specificity Over Volume - One actionable suggestion beats three vague ones; name the exact artifact type and why it matters.
- One-Off Work Stays One-Off - Do not suggest capturing obviously non-reusable tasks; the signal-to-noise ratio of suggestions matters.
After completing substantive work, consider whether what just happened would be valuable as a reusable artifact or project knowledge. Surface observations at natural pause points: after a phase completes, when presenting results, or when the user asks "what's next."
Do not suggest artifacts for obviously one-off tasks. Do not interrupt urgent work.
Artifact Candidates
Mention briefly, offer to draft via background agent:
| Type | Signal |
|---|---|
| Skill | Non-obvious technique or undocumented convention that future sessions need. |
| Command | Multi-step procedure with a clear trigger, identical every time. |
| Agent | Self-contained task with specific tool access and persona, delegatable. |
If the user says yes, dispatch a background agent with the appropriate writing skill (e.g., writing-skills, writing-commands).
Project Knowledge Candidates
Offer to add to AGENTS.md when:
- You searched for build/test/run info that was undocumented
- You made a mistake from an undocumented convention (especially after user correction)
- You discovered a non-obvious dependency or read 5+ files for a one-sentence pattern
- The user explained something not written anywhere
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 · 52 lines · 38 tokens per session scan A 1152e628f418
opportunity-awareness is a skill published in the GitHub repository axiomantic/spellbook (10 stars, last pushed 2d ago), licensed MIT. It adds 38 tokens to every session and 487 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
batch
Execute batch operations on multiple files in parallel. Automatically discovers files, splits into chunks, and processes with parallel worker agents. Use /batch followed by operation and file pattern. For many independent single-turn transforms (translate/rewrite/extract each file into a new file) that can wait…
batch-api
Prepare a many-file, single-turn transform (translate, rewrite, extract) as a plan and submit it to the asynchronous, half-price DashScope Batch API; results are delivered as new files hours later. Invoke explicitly with /batch-api.
loop
Create a loop that runs a prompt now and follows up either on a fixed schedule or through self-paced wakeups. Usage - /loop check the build, /loop 5m check the build, /loop check the PR every 30m. /loop list to show jobs, /loop clear to cancel all.
openrig-herdr
Use when opening OpenRig fleet terminals as a herdr wall — turning a rig, pod, mission, slice, or saved view into live interactive agent tiles via rig terminal, watching another rig read-only, or driving herdr on an agent's request ("open all my rigs + a mission as views"). Covers the rig terminal open|views|status…
mission-slice-sop
Use when starting, building, handing off, restoring, or closing a mission or slice under the default lightweight SDLC.
community
Use when building or running a persistent two-way community space — Discord, Telegram, Circle: platform choice, structure, onboarding, native→bot→human moderation, rituals, growth loops, health metrics. NOT churn of paying product customers (that is retention), NOT broadcast email (that is newsletter), NOT one live…