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 patrick-fu/awesome-skills --skill attention-frontiergit clone --depth 1 https://github.com/patrick-fu/awesome-skillsWrote 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/patrick-fu/awesome-skills/attention-frontier)<a href="https://agentmods.dev/skills/patrick-fu/awesome-skills/attention-frontier"><img src="https://agentmods.dev/badge/skills/patrick-fu/awesome-skills/attention-frontier/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/patrick-fu/awesome-skills/attention-frontier"><img src="https://agentmods.dev/badge/skills/patrick-fu/awesome-skills/attention-frontier.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.00803 |
| Opus 5.5 | $0.00015 | $0.00321 |
| Sonnet 5.5 | $0.00008 | $0.00161 |
| Haiku 4.5 | $0.00004 | $0.00080 |
Grade A, and why
attention-frontier 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 7d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Attention Frontier
Reduce the person's cost of surveying work, chasing progress, and recovering context while keeping important unfinished work accounted for.
Ground
Scope, incremental evidence, reconciliation. Start from the user's working scope and existing task map. Establish an initial baseline, then discover new work and read source increments. Recent activity is a discovery window, not an expiry date for older unfinished work.
Group related conversations by business matter; retain distinct user actions and unfinished side or parallel tasks, including those within one conversation. Recover the main objective and relevant backstory from source context when a recent turn only describes a local step. Reconcile candidates against current user instructions, related conversations, and relevant delivery evidence. Later resolutions must retire stale requests. Distinguish an agent's finished turn, compilation, tests, delivered artifacts, and business acceptance. Preserve the evidence level of each claim.
Select and order
Human action, ownership, business priority. Identify the next decision, review, hands-on action, or coordination that actually needs the person. Ordinary authorized execution stays with its owner. When the person's action is done and ownership continues elsewhere, move the matter to observation; bring it back when a new user action becomes ready. Reading a report alone does not complete an action.
Proactively investigate missing evidence. Remaining uncertainty belongs in a clearly labeled area with its gap and possible impact; elevate it to a user action only when the person is needed to resolve it.
Rank by explicit user priorities, deadlines and business impact, delay cost, dependencies released, and waiting time. Preserve relative order where these have not materially changed. Use judgment rather than invented deadlines, fixed scores, quotas, or Top-N limits. Keep all unfinished matters accessible, including work progressing independently and external waits.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago Changed · +4 lines 31799b19621d
- 8d ago First seen · 81 lines · 38 tokens per session scan A 861407ac2e48
attention-frontier is a skill published in the GitHub repository patrick-fu/awesome-skills (69 stars, last pushed 4d ago), licensed MIT. It adds 38 tokens to every session and 803 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-10-18.
Other skills, from other repositories
gsd-ns-manage
Invoke this Pi skill with /skill:gsd-ns-manage.
to-spec
A process for turning the current conversation into a detailed feature specification and publishing it to the project’s issue tracker.
triage-inbox
Triage academic email and calendar (Gmail / Google Calendar via the session's MCP) into a prioritized digest plus a referee-obligations tracker — classifying referee requests, R&R and editor correspondence, co-author threads, seminar and conference invites, and grant/admin deadlines, and proposing a human-gated action…
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…
dx-optimizer
Developer Experience specialist. Improves tooling, setup, and workflows. Use PROACTIVELY when setting up new projects, after team feedback, or when development friction is noticed.
document-actions
Extract cited facts, obligations, deadlines and proposed actions from documents, preserving OCR uncertainty and reconciling Prismer tasks.