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/ramybarsoum/prodkit/define-north-starnpx skills add ramybarsoum/prodkit --skill define-north-stargit clone --depth 1 https://github.com/ramybarsoum/prodkitWrote 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/ramybarsoum/prodkit/define-north-star)<a href="https://agentmods.dev/skills/ramybarsoum/prodkit/define-north-star"><img src="https://agentmods.dev/badge/skills/ramybarsoum/prodkit/define-north-star.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.1 | $0.00022 | $0.00653 |
| Opus 5 | $0.00011 | $0.00327 |
| Sonnet 5 | $0.00004 | $0.00131 |
| Haiku 4.5 | $0.00002 | $0.00065 |
Grade A, and why
define-north-star 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Interaction style: Use the
AskUserQuestiontool for all structured questions in this skill. Group related questions together (2-3 per call) rather than asking one at a time.
Define North Star Metric
When to use: During strategy planning, when metrics feel scattered, or when teams are optimizing different things
Framework source: Aakash Gupta's "Do you really need a North Star Metric?"
Quick Start
- Tell me: "Help me define our North Star metric" (or "Validate our current North Star")
- I will check
knowledge/company/business-info.mdandknowledge/strategy/for your business model, growth stage, and existing metrics - I will ask about your core value, retention drivers, and business model to narrow candidates
- We work through: Core Value identification, Metric formula (Frequency x Core Action x Breadth), Validation tests, Input metrics, and Guardrails
- Output goes to
work/analyses/north-star-[quarter].md
Key decision: Not every product needs a single North Star. Marketplaces, multi-product companies, and complex B2B may need a constellation of 2-4 metrics instead. I will help you decide which approach fits.
Context Routing Logic (Internal - for Claude)
Automatic Context Checks: When this skill is invoked, immediately check:
| Source | Files/Folders | Search Terms | What to Extract |
|---|---|---|---|
| Strategy Docs | knowledge/strategy/*.md |
objective, business goal, success metric | Current metric direction, if any |
| Business Model | knowledge/company/business-info.md |
revenue model, growth focus, metrics | What drives the business |
| Metrics History | knowledge/metrics/*.md |
baseline, trends, retention data | Current metric baselines and movement |
| Meetings | work/meeting-notes/*.md |
"North Star", "KPI", "success metric" | Stakeholder expectations |
| PRDs | projects/*/ |
success metric, target | Feature-level success indicators |
| Product Principles | knowledge/company/product-principles.md |
product principles, core values | Which principles this feature embodies and how |
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 · 56 lines · 22 tokens per session scan A c1e1a11108b4
define-north-star is a skill published in the GitHub repository ramybarsoum/prodkit (4 stars, last pushed 4mo ago), licensed MIT. It adds 22 tokens to every session and 653 once invoked, about $0.0001 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
alive:demo
Generate a believable, lived-in ALIVE world from a free-text persona description (custom path) or a deterministic sandbox preset. Routes the create/list/activate/deactivate/delete/status surface and orchestrates the 5-stage subagent generation pipeline.
alive:session-history
Revive sessions (quick or heavy), browse, and search — 'what happened recently?', 'find the session where we discussed X', 'revive yesterday's session'. For single-session recall and multi-session browsing. If the human needs to merge multiple sessions into one working context or detect conflicts between parallel…
alive:world
The human doesn't know what to work on, or wants to see everything at once. They need the big picture — what's active, what's stale, what needs attention. Renders a live world view grouped by ALIVE domain, then routes to open, tidy, find, history, or map.
cco-task
Organize work by task, track tokens/cost per task, and keep a small patchable execution state that is re-injected after /compact (SKILL.state-style) — start a task, patch its state, list tasks, or mark the active one done. Pairs with /cco-pack to load minimal context per task.
cco-templates
Manage context templates for common task types.
cco-tools
Show what tools actually cost in tokens — learned per-tool averages from observed results, replacing the hardcoded MCP/Agent guesses.