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 gnurio/nurijanian-skills --skill focal-point-findergit clone --depth 1 https://github.com/gnurio/nurijanian-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/gnurio/nurijanian-skills/focal-point-finder)<a href="https://agentmods.dev/skills/gnurio/nurijanian-skills/focal-point-finder"><img src="https://agentmods.dev/badge/skills/gnurio/nurijanian-skills/focal-point-finder/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/gnurio/nurijanian-skills/focal-point-finder"><img src="https://agentmods.dev/badge/skills/gnurio/nurijanian-skills/focal-point-finder.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.00158 | $0.02813 |
| Opus 5 | $0.00079 | $0.01406 |
| Sonnet 5 | $0.00032 | $0.00563 |
| Haiku 4.5 | $0.00016 | $0.00281 |
Grade A, and why
focal-point-finder 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 13d 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Focal Point Finder
Identify, evaluate, or create focal points in coordination and negotiation problems using Thomas Schelling's framework from The Strategy of Conflict.
A focal point is not the objectively best outcome. It is the outcome that everyone expects everyone else to expect — the one choice that stands out enough for mutual recognition. The authority is in the expectations themselves, not in the thing expectations attach to.
When to Use
- Multiple parties need to converge on a single choice (standard, deadline, meeting point, price, boundary, process)
- Communication is limited, ambiguous, or costly
- No formal authority can dictate the answer
- A proposal needs to "stick" without enforcement
- An existing default needs to be defended or displaced
Step 1: Map the Coordination Problem
Extract the structure of the situation by answering:
- Who are the parties? (List every actor who must align)
- What is being coordinated? (A location, a number, a standard, a boundary, a process, a date, a format)
- What are the communication constraints? (Full communication? Partial? Tacit? Asynchronous? Cross-cultural?)
- What happens if they fail to converge? (Cost of miscoordination — this determines urgency)
- Are interests aligned, divergent, or mixed? (Pure coordination, bargaining, or mixed-motive)
Present the map to the user for validation before proceeding.
Step 2: Scan for Existing Focal Points
Before proposing anything new, identify what focal points already exist. Check each source:
The Five Magnets
Uniqueness — Is there one option that stands alone, qualitatively different from all others? Test: "If not this, what?" — if there is no clear alternative, it is focal.
Example: On a map with many crossroads but one house, all 11 people who picked the house met. The 4 who picked crossroads each chose a different one and none met. Three houses would have destroyed the focal point — uniqueness avoids ambiguity.
What ships with it
1 file 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.
- 13d ago First seen · 205 lines · 158 tokens per session scan A 9840d3077dd1
focal-point-finder is a skill published in the GitHub repository gnurio/nurijanian-skills (107 stars, last pushed 1mo ago), licensed MIT. It adds 158 tokens to every session and 2,813 once invoked, about $0.0008 per session on Opus 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…