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/jcooley8/pincushion-pluginWrote 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/commands/jcooley8/pincushion-plugin/implement)<a href="https://agentmods.dev/commands/jcooley8/pincushion-plugin/implement"><img src="https://agentmods.dev/badge/commands/jcooley8/pincushion-plugin/implement/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/commands/jcooley8/pincushion-plugin/implement"><img src="https://agentmods.dev/badge/commands/jcooley8/pincushion-plugin/implement.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.00009 | $0.00631 |
| Opus 5.5 | $0.00004 | $0.00252 |
| Sonnet 5.5 | $0.00002 | $0.00126 |
| Haiku 4.5 | $0.00001 | $0.00063 |
Grade A, and why
implement 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 3d 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
Implement all stakeholder-approved Pincushion pins.
Workflow
- Call
implement_approved_pinsto get all approved pins grouped by page with element selectors and thread context. - If no approved or in-progress pins exist, say so and exit.
- If a git command fails with "Unable to create ... .lock: File exists", tell me which lock file it is and ask before removing it.
- For each pin:
- Call
claim_pinwith the pin's annotationId to mark it in-progress (skip if already in-progress) - Read the full thread and element context (selector, tagName, textContent)
- Use the element selector and comment to find the relevant source code (grep for the selector string, tag name, class names, or text content in the project files)
- Look up the project's traceability config from the
traceability[pin.projectId]block of theimplement_approved_pinsresponse. Defaults if absent:{ commitTrailers: 'minimal', attributionComments: 'off', recordCommitSha: true }. - Implement the requested change on your current branch (do NOT create or switch branches).
- Inline comment policy: leave a one-line
// Pincushion <pinId>: <WHY>only whenattributionCommentsis'context-warrants'AND the pin captures a non-obvious WHY (a constraint, intent, or rationale not self-evident from the diff). Skip for cosmetic fixes (typos, color tweaks, copy edits). When'always', leave the comment regardless. When'off'(default), never. - Commit using the trailer block matching the project's
commitTrailers:'minimal'(default):git commit -m "pincushion: <description>" -m "Pin-ID: <pinId>"'standard': also includeReviewed-By: <pin.approvedBy>on a new line — but ONLY ifapprovedBydiffers from yourgit config user.email(skip self-approval; double-attributing the same person is noise).'full': standard plusPincushion-Pin-Url: <pin.pincushionPinUrl>.- Use a multi-line
-mbody or a single-m "$(cat <<'EOF'\n...\nEOF\n)"HEREDOC to fit all trailers cleanly. - Per-shell kill switch: if env
PINCUSHION_TRAILERS=offis set, fall back to'minimal'regardless of project preset.
- Capture the commit SHA:
SHA=$(git rev-parse HEAD). Pass it tofix_and_resolve({ annotationId, fixDescription, commitSha: SHA }). The MCP records it on the annotation only ifrecordCommitShais true (default).
- Call
- Summarize what was implemented.
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.
- 3d ago First seen · 27 lines · 9 tokens per session scan A 9ade787ee538
implement is a command published in the GitHub repository jcooley8/pincushion-plugin (1 stars, last pushed 4d ago), licensed MIT. It adds 9 tokens to every session and 631 once invoked, about $0.0000 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-23.
Other commands, from other repositories
project-proposal
Generate design proposals with scope of work, concept overview, phasing, fee structure, and terms.
spec-sheet
Draft FF&E schedules and material specifications with manufacturer details, dimensions, and lead times.
extract-screens
Analyze user stories in the current project and extract screens + reusable UI components into project-management/screens/ and project-management/components/. Requires user stories in project-management/user-stories/.
execute
Land audit batches on the audit path — fence verified first, items stay blocked until merge.
profile
Save, load, inspect, update, reset, or delete diagram-design client profiles.
setup-workflow
Set up a design team workflow and rituals.