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 fledgeling-co/fledgeling-plugins --skill positioninggit clone --depth 1 https://github.com/fledgeling-co/fledgeling-pluginsWrote 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/fledgeling-co/fledgeling-plugins/positioning)<a href="https://agentmods.dev/skills/fledgeling-co/fledgeling-plugins/positioning"><img src="https://agentmods.dev/badge/skills/fledgeling-co/fledgeling-plugins/positioning/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/fledgeling-co/fledgeling-plugins/positioning"><img src="https://agentmods.dev/badge/skills/fledgeling-co/fledgeling-plugins/positioning.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.00316 | $0.03547 |
| Opus 5.5 | $0.00126 | $0.01419 |
| Sonnet 5.5 | $0.00063 | $0.00709 |
| Haiku 4.5 | $0.00032 | $0.00355 |
Grade A, and why
positioning 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 — 285 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Positioning
What this replaces
positioning-pipeline:positioning-pipeline (DiologIR, 1.0.1) wrote two Gemini Deep Research prompts
and a launcher page with copy buttons, then asked the user to run the research
in a browser and come back with the output. Its four-book grounding and its
territory template were good enough to keep, and they are carried forward here
with credit. What changed is that every quality control now sits inside the
pipeline: the research runs here, the citations get verified here, the claims get
counted here, and the honesty rules that were prose are commands with exit codes.
The manual Gemini lane still exists and is still sometimes the right call —
references/gemini-lane.md keeps it. It is a lane, not the spine.
Where everything lands
One directory, fixed, so a second run finds the first one's work and a reader knows where to look without being told.
docs/positioning/
├── 00-decision.md the recommendation and the case for it
├── 10-territory-<slug>.md one per shortlisted territory
├── 20-category-and-competitors.md
├── 30-customer-evidence.md
├── 40-evidence-register.md the claim ledger, rendered
├── 50-product-truth.md the truth table, rendered
├── 60-candidates-cut.md
├── 70-research-decision.md what was bought, and what was not
├── 80-pre-commitment-tests.md
├── positioning-report.html the designed decision surface
├── DESIGN.md the brand system, when this run authored it
├── research/ every exported panel report + its source registry
└── work/ ledger.json, gate output, scratch
What ships with it
25 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.
- assets/prompt-launcher.template.html 16 KB
- assets/report.template.html 11 KB
- assets/templates/candidates-cut.template.md 1.3 KB
- assets/templates/category.template.md 2.9 KB
- assets/templates/customer.template.md 1.9 KB
- assets/templates/decision.template.md 1.6 KB
- assets/templates/evidence-register.template.md 1.6 KB
- assets/templates/pre-commitment.template.md 1.8 KB
- assets/templates/product-truth.template.md 1.0 KB
- assets/templates/research-decision.template.md 1.7 KB
- assets/templates/territory.template.md 3.8 KB
- gemini.md 27 KB
- references/candidate-generation.md 8.5 KB
- references/decision-aid.md 11 KB
- references/evidence.md 19 KB
- references/gemini-lane.md 3.5 KB
- references/gemini-prompt-architecture.md 5.6 KB
- references/positioning-frameworks.md 9.7 KB
- references/product-research-persona.md 3.4 KB
- references/product-truth.md 4.3 KB
- references/report-design.md 5.5 KB
- references/report-suite.md 5.2 KB
- references/research-panels.md 14 KB
- scripts/claim_ledger.py 13 KB runs code
- scripts/positioning_lint.py 12 KB runs code
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 · +14 tokens per session a05813a78b99
- 1mo ago First seen · 285 lines · 302 tokens per session scan A 504401f60bb8
positioning is a skill published in the GitHub repository fledgeling-co/fledgeling-plugins (2 stars, last pushed 4d ago), licensed MIT. It adds 316 tokens to every session and 3,547 once invoked, about $0.0013 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-04.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…