Borrowing it
Nothing to install: this file belongs to sponge-b0b/Polaris. 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/sponge-b0b/Polaris/main/.agents/skills/attention/SKILL.mdgit clone --depth 1 https://github.com/sponge-b0b/PolarisWrote 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/sponge-b0b/polaris/attention)<a href="https://agentmods.dev/skills/sponge-b0b/polaris/attention"><img src="https://agentmods.dev/badge/skills/sponge-b0b/polaris/attention/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/sponge-b0b/polaris/attention"><img src="https://agentmods.dev/badge/skills/sponge-b0b/polaris/attention.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.00020 | $0.02044 |
| Opus 5.5 | $0.00008 | $0.00818 |
| Sonnet 5.5 | $0.00004 | $0.00409 |
| Haiku 4.5 | $0.00002 | $0.00204 |
Grade A, and why
attention 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Attention
$attention is Polaris's reusable report-only concern-surfacing skill.
It exists to prevent an agent from silently proceeding past something material merely because the current task, checklist, tests, or workflow did not explicitly ask the right question.
The always-on duty lives in AGENTS.md. This skill provides a deliberate sweep for formal workflow checkpoints.
A formal sweep result is a checkpoint-local snapshot, not a terminal state for Attention. ATTENTION: CLEAR means only that the completed bounded sweep found no material concern at that checkpoint. It never suspends, satisfies, or exhausts the standing duty to notice and surface material concerns during later analysis, mutation, verification, or handoff.
Polaris-Wide Scope
The current artifact, diff, ticket, Spec, or workflow checkpoint is the immediate work surface, not the boundary of Attention.
Every deliberate sweep must also evaluate what the current observation implies for Polaris as a whole, using the relevant durable system model already recoverable from authority. Consider, when materially implicated, product intent, domain semantics, architecture, authority, code, persistence, APIs, tests, documentation, Living Entity Wiki knowledge, workflow skills, tracker/lifecycle/governance state, and upstream/downstream contracts.
Do not wait for the repository owner to notice a broader consequence first.
Use this materiality threshold:
Would a competent architect who understood Polaris as a whole want this brought to their attention now?
If yes, surface it. If no, continue without distraction.
Polaris-wide scope does not authorize a whole-repository audit after every edit. Inspect the smallest broader surface necessary to test a material concern or consequence exposed by the current work.
Authority Boundary
Attention may:
- notice;
- inspect;
- compare against authority;
- challenge assumptions;
- surface concerns;
- recommend routing or questions.
Attention may not:
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 Changed · +5 lines 75b1a1cf40c7
- 1mo ago Changed · +3 lines fdee13d1aa2c
- 1mo ago Changed · +32 lines · +2 tokens per session a55ee2bfb832
- 1mo ago First seen · 150 lines · 18 tokens per session scan A 32e81ee774a4
attention is a skill published in the GitHub repository sponge-b0b/Polaris (4 stars, last pushed today), licensed Apache-2.0. It adds 20 tokens to every session and 2,044 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-09-08.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.