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 agentmods add skills/febradc-github/turnstile/turnstile-brainstormnpx skills add febradc-github/turnstile --skill turnstile-brainstormgit clone --depth 1 https://github.com/febradc-github/turnstileWrote 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/febradc-github/turnstile/turnstile-brainstorm)<a href="https://agentmods.dev/skills/febradc-github/turnstile/turnstile-brainstorm"><img src="https://agentmods.dev/badge/skills/febradc-github/turnstile/turnstile-brainstorm.svg" alt="Measured on agentmods" 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 | $0.00058 | $0.00784 |
| Opus 5 | $0.00029 | $0.00392 |
| Sonnet 5 | $0.00012 | $0.00157 |
| Haiku 4.5 | $0.00006 | $0.00078 |
Grade A, and why
turnstile-brainstorm 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 5d 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 — 32 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorm
Process
- Search the vault for notes related to the idea's topic ($ARGUMENTS). Surface anything relevant, including conflicts, before continuing. If the idea already exists in the backlog or a sprint, point that out and ask whether they mean to extend the existing item instead (route to that item's gate, not refine, which only mints new ids).
- Run an open-ended, one-question-at-a-time dialogue to explore:
- What problem this actually solves and for whom.
- The rough shape of an approach -- just enough to know it's worth formalizing.
- How it sits in the existing system: which components it touches, and whether any architecture or decision note from step 1 supports or conflicts with it. Surfacing a conflict here is cheaper than discovering it in refine.
- Alternatives briefly considered and why this direction seems right. If the idea stays vague after several rounds, keep asking narrower open-ended questions; do not force a summary or hand off without an actual problem statement.
- Pitch panel (gated -- see rules above). If epic-scale or requested, offer the panel; on yes, dispatch
pitch-agentthree times in parallel, one stance each -- minimalist, skeptic, scout (swap in a custom stance if the user names one). Each dispatch gets only: a two-or-three-sentence idea summary, the stance, and the relevant step-1 vault findings. Never the dialogue transcript. - Synthesize the pitches yourself: deduplicate, keep genuinely distinct directions (usually 2-3), present each with its strongest argument and biggest risk. If the pitches all converge, say so honestly and present one direction -- do not manufacture fake disagreement. A pitch contradicting a recorded ADR is the skeptic doing its job -- surface it. The user picks, mixes, or rejects; panel output is advisory, never a decision.
- Keep exploring until the idea is concrete enough that
turnstile-refinecould immediately start its own stricter questions without re-deriving the problem statement. - Summarize the idea in two or three sentences and confirm it's ready to formalize.
- Once confirmed, invoke
turnstile-refinewith the summary as its starting description -- including architecture observations, tentative design directions, and the panel's rejected directions with why (refine's curator dispatch records the decision trail; brainstorm itself writes nothing).
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.
- 5d ago First seen · 32 lines · 58 tokens per session scan A f3bb6dc36353
turnstile-brainstorm is a skill published in the GitHub repository febradc-github/turnstile (1 stars, last pushed 1mo ago), licensed MIT. It adds 58 tokens to every session and 784 once invoked, about $0.0003 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-31.
Other skills, from other repositories
chief-revenue-officer
Owns the revenue engine end to end: sales, monetization, pricing, customer success, retention, and partnerships. Use this for pricing and packaging decisions, sales strategy and coverage, forecast and pipeline health, churn and expansion, partner and channel strategy, or when marketing-sourced demand is not…
chief-strategy-officer
Owns where the business plays and how it wins over a multi-year horizon — portfolio choices, corporate development, strategic partnerships, and planning under uncertainty. Use this for a decision about which markets or businesses to be in, whether to build, buy, or partner, how to allocate capital across business…
seo-strategy
Audits and improves organic search performance — technical health, site architecture, internal linking, structured data, and the content decisions that determine what can rank. Use this to run an SEO audit, diagnose why pages are not ranking or were deindexed, plan a site's URL and navigation structure, add structured…
financial-statement-analysis
Reads a set of financial statements and establishes what changed and why — fluctuation analysis against prior period and against budget, profitability, liquidity, solvency and efficiency ratios, benchmarking, and the non-GAAP measures presented alongside them. Use this to interpret results, review a counterparty's or…
youtube-producer
Plans, packages, and scripts long-form video for retention and channel growth — idea selection, titles and thumbnails, script structure, and diagnosing why a video or channel underperforms. Use this for video ideas, packaging, scripting, a retention teardown, or channel strategy — including when someone describes a…
estimating-and-contingency
Produces a cost or effort estimate someone can defend — decomposing the work, choosing between analogous, parametric and bottom-up methods, documenting the basis and its assumptions, expressing confidence as a range, and sizing contingency and management reserve separately. Use this to build an estimate, challenge one…