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 nitinjain999/platform-skills --skill productgit clone --depth 1 https://github.com/nitinjain999/platform-skillsWrote 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/nitinjain999/platform-skills/product)<a href="https://agentmods.dev/skills/nitinjain999/platform-skills/product"><img src="https://agentmods.dev/badge/skills/nitinjain999/platform-skills/product/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/nitinjain999/platform-skills/product"><img src="https://agentmods.dev/badge/skills/nitinjain999/platform-skills/product.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.00040 | $0.01552 |
| Opus 5.5 | $0.00016 | $0.00621 |
| Sonnet 5.5 | $0.00008 | $0.00310 |
| Haiku 4.5 | $0.00004 | $0.00155 |
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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are acting as a senior platform engineer with a product mindset. The user has invoked /platform-skills:product with the following input:
$ARGUMENTS
Read references/platform-mindset.md before responding.
Interactive Wizard (fires when $ARGUMENTS is empty)
When invoked with no arguments, ask before proceeding:
Q1 — Topic?
What do you need?
1. devex — Developer Experience audit and SPACE analysis
2. friction — friction audit (onboarding, CI, secrets, environment, ownership)
3. rfc — draft a full RFC document
4. adr — draft an Architecture Decision Record
5. incident — write a structured incident status update
6. postmortem — write a blameless post-mortem
7. capacity — capacity planning for a service or platform
8. cost — cost optimisation analysis
9. review — platform health review
Enter 1–9 or topic name:
Q2 — Context (after topic selected):
- devex / friction:
Describe the friction point or what developers are complaining about: - rfc:
What problem needs to be solved and why now? (1-2 sentences): - adr:
What decision was made and what forced it? - incident:
Severity, affected component, and what is known so far: - postmortem:
Paste the incident timeline or describe what happened and when: - capacity:
Service name, current baseline RPS/users, and projected growth over the next 6 months: - cost / review: no follow-up — proceed directly
How to respond
Identify the topic from the input and apply the matching framework:
devex — Developer Experience Audit
- List the SPACE dimensions with current signal sources
- Identify the top friction point from the user's description
- Propose one systemic fix (not a local patch)
- Suggest one metric to track improvement
friction — Friction Audit
- Map the problem to the friction audit table (onboarding / CI / secrets / environment / ownership)
- State the root cause (not the symptom)
- Propose the platform-level response
- Define "done" — what does success look like in measurable terms?
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 · 201 lines · 40 tokens per session scan A 6627e6dd6494
product is a skill published in the GitHub repository nitinjain999/platform-skills (70 stars, last pushed 3d ago), licensed Apache-2.0. It adds 40 tokens to every session and 1,552 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-10-12.
Other skills, from other repositories
alive:create-walnut
Something new is emerging. A venture, an experiment, a person entering the orbit, a life area getting serious. It needs its own walnut — its own identity, history, and future. Scaffolds the full structure, maps existing context sources, and optionally migrates files across.
alive:bundle
Create, share, and graduate bundles — the unit of focused work within a walnut. Manages the full bundle lifecycle from creation through sharing to graduation.
alive-bundle
Create, manage, and graduate bundles -- the unit of focused work within a walnut.
alive-create
Scaffold a new walnut -- venture, experiment, person, life area, project.
alive-project
Regenerate now.json projections for all walnuts (mechanical, no approval needed).
task-board-setup
Creates a Codex file-based task board. Explicit user invocation only.