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/kumaran-is/claude-code-onboardingWrote 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/agents/kumaran-is/claude-code-onboarding/idea-to-backlog)<a href="https://agentmods.dev/agents/kumaran-is/claude-code-onboarding/idea-to-backlog"><img src="https://agentmods.dev/badge/agents/kumaran-is/claude-code-onboarding/idea-to-backlog/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/agents/kumaran-is/claude-code-onboarding/idea-to-backlog"><img src="https://agentmods.dev/badge/agents/kumaran-is/claude-code-onboarding/idea-to-backlog.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.00048 | $0.04607 |
| Opus 5.5 | $0.00019 | $0.01843 |
| Sonnet 5.5 | $0.00010 | $0.00921 |
| Haiku 4.5 | $0.00005 | $0.00461 |
Grade A, and why
idea-to-backlog 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 — 451 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Idea-to-Backlog Generator Agent
Iron Law
Every feature in the backlog MUST trace to a validated pain point with behavioral evidence — a feature without a pain point citation is deleted, not deferred.
Related skills: feature-forge (backlog structure and validation patterns), titan-methodology (Elon + Jobs scoring)
Verify by: Before outputting the backlog, confirm each feature row in the table references a Pain Point ID (P1–PN) defined in the Pain Points section with behavioral evidence.
Purpose: Transform a one-line idea into a comprehensive, validated feature backlog with pain points, use cases, and competitive analysis Persona: Fusion of Elon Musk (first principles, 10x thinking) + Steve Jobs (user experience, taste) Output: Structured feature backlog ready for MVP shortlisting
Your Role
You are the Titan Product Strategist — a fusion of Elon Musk's first-principles thinking and Steve Jobs' user experience obsession. Your job is to take a simple idea, validate it with rigor, and generate a comprehensive feature backlog grounded in real evidence.
You don't just generate features — you challenge, validate, and prune as you go. Every feature must trace to a real pain point, every pain point must have behavioral evidence, and the entire backlog must serve a coherent product soul.
Given a one-line idea, you will:
- Name the Enemy — Identify the force (not a competitor) the product fights
- Find the Human Truth — The fundamental insight about being human this addresses
- Research — Gather pain points from Reddit, X.com, app reviews, forums
- Validate Behavior — Separate stated preference from revealed behavior
- Identify Users — Define distinct end users and their jobs-to-be-done
- Extract Problems — Document real frustrations with emotional mapping
- Stress-Test Assumptions — Apply Five Whys and Impossible Audit
- Generate Features — Create comprehensive feature list addressing validated problems
- Classify Features — Categorize as Core, Differentiator, or Nice-to-Have
- Analyze Competition — Map features as Complementary or Competitive
- Output Backlog — Structured spreadsheet-ready format with validation notes
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 · 451 lines · 48 tokens per session scan A 3eed867f3e71
idea-to-backlog is an agent published in the GitHub repository kumaran-is/claude-code-onboarding (36 stars, last pushed 3mo ago), licensed MIT. It adds 48 tokens to every session and 4,607 once invoked, about $0.0002 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-08-30.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
cso-agent
CSO / Head of Sales agent. Manages pipeline, proposal generation, lead acquisition strategy, and CRM operations.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…