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.
git 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/plugins/fledgeling-co/fledgeling-plugins/positioning)<a href="https://agentmods.dev/plugins/fledgeling-co/fledgeling-plugins/positioning"><img src="https://agentmods.dev/badge/plugins/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/plugins/fledgeling-co/fledgeling-plugins/positioning"><img src="https://agentmods.dev/badge/plugins/fledgeling-co/fledgeling-plugins/positioning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
What it actually says
{
"name": "positioning",
"description": "Decide what a product should stand for, and be able to show your working. Runs its own Dossier deep-research panels (free CLI lane plus paid API lane, one or more panels decomposed by archetype) rather than emitting prompts for a human to paste elsewhere; generates candidate positions under trawl's persona frame portfolio BEFORE the research runs so the panels discriminate rather than describe; then binds every positioning move to a claim id and a product-truth row in a ledger whose check command fails when a hero line rests on capability that has not shipped, on a citation nobody verified, or on a confidence label claimed across too few independent registrable domains. Replaces the predecessor's weighted-slider scorer, which all four research panel members independently found documented-unsafe for a 3-5 option strategic choice, with vetoes, a natural-unit consequence table, dominance screening, even swaps, rank stability across plausible weights, scenario regret, and a permitted no-decision output. Ships nine templated markdown reports plus one designed interactive HTML decision surface built through design-craft:design-craft and ux-craft:ux-craft, with GSAP where scroll carries the argument, Three.js only where the strategy canvas needs a real volume, media-gen-pro for imagery and mermaid for diagrams, taking the project's DESIGN.md when it has one and authoring one when it does not, gated by a design-review:design-review pass before anyone sees it. Use for positioning or re-positioning a product, choosing between positioning options, market or competitor or customer research behind a positioning decision, messaging architecture, naming a category, finding a beachhead, or \"work out how to market this\" — including \"positioning pipeline\". Rebuild of positioning-pipeline by DiologIR.",
"version": "0.2.1",
"author": {
"name": "Fledgeling",
"email": "[email protected]"
}
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 316 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 1123f4b11712
- 1mo ago First seen · 10 lines scan A 8bdae92f033a
positioning is a plugin published in the GitHub repository fledgeling-co/fledgeling-plugins (2 stars, last pushed 4d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
themes-example
themes-example. An open-source AI agent that brings the power of Gemini directly into your terminal.
claude-plugins-official marketplace
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations.
knowledge-work-plugins marketplace
Plugin marketplace listing 123 plugins: noibu, productivity, enterprise-search, cowork-plugin-management, sales.
code-modernization
Guided modernization for any legacy codebase: start with /modernize, get an assessment, an interactive map, the business rules mined from the code, and a plan you approve, then an upgrade, a rewrite or a rebuild with independent proof that the new code behaves like the old. Includes security hardening, a one-page…