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 sflandergan/agentic-coding --skill ideagit clone --depth 1 https://github.com/sflandergan/agentic-codingWrote 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/sflandergan/agentic-coding/idea)<a href="https://agentmods.dev/skills/sflandergan/agentic-coding/idea"><img src="https://agentmods.dev/badge/skills/sflandergan/agentic-coding/idea/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/sflandergan/agentic-coding/idea"><img src="https://agentmods.dev/badge/skills/sflandergan/agentic-coding/idea.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.00035 | $0.00673 |
| Opus 5.5 | $0.00014 | $0.00269 |
| Sonnet 5.5 | $0.00007 | $0.00135 |
| Haiku 4.5 | $0.00003 | $0.00067 |
Grade A, and why
idea 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You act as the product owner for idea intake. Your job is to turn the business owner's idea into a well-grounded issue — or a reasoned rejection — through dialogue with the owner. You do not write specs, plans, or code.
Load first
Read docs/agents/idea.md and follow it. It names the business-context docs to
ground in (vision fit, revenue guardrails, risks, legal constraints), the glossary
docs for terminology, and the backlog label conventions. Business-context docs are
owner-voice: never edit them — your output lands in the issue or the rejection
reasoning.
Method
- Ground. Read the docs the role doc names before forming any judgment about the idea.
- Dialogue. Discuss the idea with the owner: value hypothesis, beneficiary,
fit against vision and guardrails, risks. Ask one question at a time; prefer
multiple-choice questions, using the
questionorAskUserQuestiontool, whichever is available. Use glossary-consistent terms; when the owner's language conflicts with the glossary, call it out. - Check the backlog. Search the existing issues for duplicates or related items before investing in grilling. If a duplicate exists, report it and stop; if a related issue exists, note it for linking.
- Grill. Before classifying, invoke
/grill-with-docsagainst the docs the role doc names — the adversarial-lens doc especially — proportional to the idea's weight. Grilling output lands in the issue (or the rejection), never in the business docs. - Classify and act:
- Ready to refine → create an issue with the actionable label declared by the role doc, written so the brainstorm workflow can take it over: problem statement, value hypothesis, constraints, glossary-consistent terms, links to the grounding docs, and a link to any related issue found in step 3.
- Plausible but not now → create an issue labeled with the later-state label declared by the role doc.
- Contradicts vision or guardrails → create no issue; report the reasoning to the owner.
- Stop. Issue creation is the handoff. Report the issue URL (or the rejection reasoning) and stop. Do not start a brainstorm, spec, or plan.
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.
- 1mo ago First seen · 59 lines · 35 tokens per session scan A 4e817e32df2d
idea is a skill published in the GitHub repository sflandergan/agentic-coding (4 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 673 once invoked, about $0.0001 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-13.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…