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 perniemann/pnCore --skill pn-business-strategy-orchestrationgit clone --depth 1 https://github.com/perniemann/pnCoreWrote 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/perniemann/pncore/pn-business-strategy-orchestration)<a href="https://agentmods.dev/skills/perniemann/pncore/pn-business-strategy-orchestration"><img src="https://agentmods.dev/badge/skills/perniemann/pncore/pn-business-strategy-orchestration/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/perniemann/pncore/pn-business-strategy-orchestration"><img src="https://agentmods.dev/badge/skills/perniemann/pncore/pn-business-strategy-orchestration.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.00060 | $0.02590 |
| Opus 5 | $0.00030 | $0.01295 |
| Sonnet 5 | $0.00012 | $0.00518 |
| Haiku 4.5 | $0.00006 | $0.00259 |
Grade A, and why
pn-business-strategy-orchestration 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 9d 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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Business Strategy Orchestration
When to use
- Loaded automatically by the
business_strategyworkflow (step 0). Do not load directly; use/pn-strategyorworkflow_step({ workflow_type: "business_strategy", ... }). - Referenced by all subsequent steps as the canonical behavioral contract for the run.
Workflow identity
Entry point: /pn-strategy command (or workflow_step("business_strategy", 0, {}))
Steps: 9 (indices 0–8); two are conditional (step 1 on mode, step 6 on includesImplementation).
Single source of truth for verdict: pn-pressure-test 6-row scorecard (pain intensity, buyer clarity, urgency, differentiation, speed to validate, founder advantage). No competing rubric.
Deliverables: docs/strategy/[slug]-strategy-brief.md (machine-facing digest, canonical data source) + docs/strategy/[slug]-strategy-brief.html (human-facing stakeholder brief, built from the same evidence using its own template — not transformed from the markdown).
Workflow state shape
business_strategy.mode : "idea" | "codebase" | "hybrid"
business_strategy.repoPath : string (when mode != "idea")
business_strategy.framing : { problem, audience, hypotheses[] }
business_strategy.candidates : Array<{id, icp, value_prop_sentence, monetization_hypothesis, evidence_refs[file:line]}>
business_strategy.selectedAngle : string // candidate id chosen at step 1
business_strategy.evidenceLogPath : string // ".pncore/workflow-handoff.jsonl"
business_strategy.frames : { market_sizing, comps, jtbd, biz_model, risks }
business_strategy.includesImplementation : boolean
business_strategy.grillComplete : boolean
business_strategy.discussionIterations : number // Weak loop counter; cap = 2
business_strategy.iterationCapApproved : boolean // set after approval_checkpoint when cap exceeded
business_strategy.pressureTestVerdict : "Strong" | "Weak" | "Pivot"
business_strategy.killCriteria : string
business_strategy.firstTenCustomers : string
business_strategy.skepticVerdict : "proceed" | "revise" | "skipped"
business_strategy.verdictLocked : boolean
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.
- 9d ago First seen · 182 lines · 60 tokens per session scan A a009ef0d68b3
pn-business-strategy-orchestration is a skill published in the GitHub repository perniemann/pnCore (0 stars, last pushed 6d ago), licensed MIT. It adds 60 tokens to every session and 2,590 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
typescript
TypeScript coding conventions, best practices, and patterns for writing clean, maintainable code.
deepseek-harness
Use when building AI agent applications with a plugin-based architecture — Web UI, CLI, Python SDK, Cordis plugin system, multi-model orchestration. DeepSeek Harness (dsh): open-source agent harness by DeepSeek AI where everything is a plugin, powered by Cordis for spatiotemporal composability.
typescript-development
You MUST activate this skill when working on TypeScript or JavaScript projects.
js-gof
Apply Gang of Four and related design patterns in JavaScript and TypeScript. Use when implementing creational, structural, or behavioral patterns, or when the user mentions factories, builder, prototype, flyweight, singleton, object pool, adapter, wrapper, decorator, proxy, bridge, composite, facade, chain of…
error-handling
Apply error handling and recovery patterns in JavaScript/TypeScript or Node.js. Use when implementing error handling, retry logic, or when the user mentions domain errors, error recovery, error escalation.
senior-frontend
Frontend development skill for React, Next.js, TypeScript, and Tailwind CSS applications. Use when building React components, optimizing Next.js performance, analyzing bundle sizes, scaffolding frontend projects, implementing accessibility, or reviewing frontend code quality.