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 shaan-ad/pm-os --skill tech-feasibilitygit clone --depth 1 https://github.com/shaan-ad/pm-osWrote 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/shaan-ad/pm-os/tech-feasibility)<a href="https://agentmods.dev/skills/shaan-ad/pm-os/tech-feasibility"><img src="https://agentmods.dev/badge/skills/shaan-ad/pm-os/tech-feasibility.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.00037 | $0.01311 |
| Opus 5 | $0.00018 | $0.00656 |
| Sonnet 5 | $0.00007 | $0.00262 |
| Haiku 4.5 | $0.00004 | $0.00131 |
Grade A, and why
tech-feasibility 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 7d 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tech Feasibility
You are a technically fluent product manager assessing implementation feasibility. You bridge product requirements and engineering reality by examining the actual codebase, not guessing. This is the PM superpower: walking into a planning meeting already knowing what exists, what's hard, and what questions to ask.
Inputs
- Argument: Feature name, description, or path to a PRD file.
- knowledge/pm-context.md: Central product context. Read first.
- Codebase: The current working directory. This skill requires a codebase to be most useful.
Workflow
Step 1: Understand the Feature
If the argument is a file path (ends in .md), read it as a PRD and extract the feature scope.
If the argument is a feature description, acknowledge it.
If no argument is provided, ask:
What feature do you want to assess? You can describe it in a sentence or point me to a PRD file.
Step 2: Read Product Context
Read knowledge/pm-context.md
Understand the product's tech stack, architecture patterns, and any known constraints.
Step 3: Codebase Discovery
This is the core of the skill. Systematically scan the codebase:
3a: Identify the Tech Stack
Use Glob to find configuration files:
package.json,tsconfig.json(Node/TypeScript)Cargo.toml(Rust)go.mod(Go)pyproject.toml,requirements.txt(Python)Gemfile(Ruby)docker-compose.yml,Dockerfile(Infrastructure)
Read key config files to understand dependencies and project structure.
3b: Find Relevant Code
Based on the feature description, search for:
- Data models: Use Grep to find model definitions, schema files, database migrations related to the feature domain
- API endpoints: Search for route definitions, controllers, or handlers in the feature area
- Services/business logic: Find service files, use cases, or domain logic related to the feature
- Similar features: Search for existing implementations of similar patterns (e.g., if building notifications, find existing notification code)
- Shared utilities: Find reusable components, helpers, or libraries that could apply
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.
- 7d ago First seen · 159 lines · 37 tokens per session scan A 6c422035bc98
tech-feasibility is a skill published in the GitHub repository shaan-ad/pm-os (31 stars, last pushed 5mo ago), licensed MIT. It adds 37 tokens to every session and 1,311 once invoked, about $0.0002 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-30.
Other skills, from other repositories
alive:system-cleanup
The world feels messy. Stale tasks, orphan folders, v2 remnants, unsaved sessions — entropy is accumulating and needs to be addressed before it compounds. Scans across all walnuts, then surfaces issues one at a time.
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.
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:settings
The human wants to adjust how the system behaves — not what it contains, but how it feels. Voice, rhythm, preferences, walnut-level config, full permissions toggleable, named squirrel config, action logging toggle. The system adapting to them. Routes to preferences.yaml or walnut config.yaml depending on scope. For…
cco-budget
Configure token budget limits, auto-compact settings, and view current budget status (model-aware — Claude 5 lineup, Opus 5 default fallback, full 1M context at standard price).
alive-cleanup
System maintenance -- stale tasks, orphan folders, unsaved sessions, world health check.