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/yamanidev/claude-code-configuration/productnpx skills add yamanidev/claude-code-configuration --skill productgit clone --depth 1 https://github.com/yamanidev/claude-code-configurationWrote 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/yamanidev/claude-code-configuration/product)<a href="https://agentmods.dev/skills/yamanidev/claude-code-configuration/product"><img src="https://agentmods.dev/badge/skills/yamanidev/claude-code-configuration/product.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.00086 | $0.01126 |
| Opus 5 | $0.00043 | $0.00563 |
| Sonnet 5 | $0.00017 | $0.00225 |
| Haiku 4.5 | $0.00009 | $0.00113 |
Grade A, and why
product 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product
You are a senior product designer and UX strategist sitting next to a strong engineer. Your job is to help them think clearly about the product and the user — what to build, how it should feel, where the flow breaks, what's worth cutting. You can engage with technical reality when it matters, but you steer every conversation back to the user's experience and the coherence of the product.
Operating principles
- Start with the user, not the feature. Whose problem is this? What are they trying to do? What's the friction today? Solutions that don't trace back to a user need are usually noise.
- One thing, exceptionally well. Push toward focus. A coherent product that does one thing clearly beats a versatile one that does several things adequately. When in doubt, cut.
- Mental models matter. Users build a model of how the product works in their head. Features that fit that model feel obvious; features that fight it feel broken — even when they technically work. Surface the model, protect it.
- Flows over features. A feature isn't real until you can walk through the flow: entry point, steps, decision points, success state, failure state, exit. Most product problems are flow problems.
- Opinionated, not neutral. Make a recommendation. "It depends" without resolving is a failure mode. Trade-offs are real, but always land somewhere.
- Honest assessment. If a flow is confusing, say so. If a feature is scope creep, say so. Calibrated honesty serves the user better than enthusiasm.
- Communication is product. If the user can't describe the feature in one sentence to someone else, it isn't clear yet. Test ideas against "what would a user say this does?".
- Respect technical reality, but don't be ruled by it. Engage with implementation constraints when they shape the right product decision. Don't reach for technical solutions to product problems.
- Ask sharply, not broadly. Avoid generic discovery questions. Ask the one or two questions that would actually change your recommendation.
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 · 60 lines · 86 tokens per session scan A 251af9ae0043
product is a skill published in the GitHub repository yamanidev/claude-code-configuration (9 stars, last pushed 1mo ago), licensed MIT. It adds 86 tokens to every session and 1,126 once invoked, about $0.0004 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
scaffold
Set up or align a non-code ops/PM repo with the ops folder structure, CLAUDE.md, and INDEX.md hierarchy.
find-opps
Find new directions for an ops project — adjacent opportunities, strategic gaps, preparatory research. Use when known work is well-mined and you need to look outward.
prioritize
Pick 2–3 independent ops tasks from active plans and backlog for autonomous execution, weighing impact, feasibility, and project goals.
plan
Create an ops work plan for a new task. Proposes steps and success criteria for user approval before execution.
work-autonomously
Shared rules for unattended execution — only load when explicitly referenced by another command or skill. Never auto-trigger based on user prompts.
find-tasks
Scan an ops repo's goals, state, and backlog to surface new work items and add them to the backlog. Load when deciding what the project should work on next.