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 aleksander-dytko/ai-pm-workspace --skill guidegit clone --depth 1 https://github.com/aleksander-dytko/ai-pm-workspaceWrote 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/aleksander-dytko/ai-pm-workspace/guide)<a href="https://agentmods.dev/skills/aleksander-dytko/ai-pm-workspace/guide"><img src="https://agentmods.dev/badge/skills/aleksander-dytko/ai-pm-workspace/guide/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/aleksander-dytko/ai-pm-workspace/guide"><img src="https://agentmods.dev/badge/skills/aleksander-dytko/ai-pm-workspace/guide.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.00016 | $0.04975 |
| Opus 5.5 | $0.00006 | $0.01990 |
| Sonnet 5.5 | $0.00003 | $0.00995 |
| Haiku 4.5 | $0.00002 | $0.00498 |
Grade A, and why
guide 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 1mo 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 — 344 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Guide
An interactive tour through the shipped skills. Each module teaches one skill by running it against sample data in samples/. Designed for PMs, designers, analysts, or engineers - the skill adapts framing to the role set in CLAUDE.md.
Pre-emit checklist (run BEFORE every chat message in this skill)
Before you send any message while /guide is active, audit your draft against these rules. If any fails, fix it before sending.
- Vault paths are backticked. Any token that looks like a file path (contains
/or ends in.md) must be wrapped in backticks so Claude Code renders it as a clickable reference. A path without backticks is a bug - it renders as plain text and the user can't click it. - File-argument commands use
@. When you tell the user how to run a skill with a file input, the path must be@-prefixed so Claude Code's file autocomplete activates:`/meeting @samples/sample-meeting-transcript.md`, not`/meeting samples/sample-meeting-transcript.md`. - Module intros below are printed verbatim. Each module has a literal intro block in this file. Print that block exactly as written - do not rephrase, do not add extra paragraphs, do not strip backticks. The blocks are short on purpose.
- Gate order. If the current turn is a first-run orientation, a resume, or a numeric jump, the message ends with
Ready to start Module N? (y/n/skip)and nothing else - no module intro on the same turn. If the user just typednext, there is NO gate - go straight to the next module's verbatim intro.
Progress tracking
Progress is stored in .claude/memory/guide-progress.md. The .claude/memory/ directory ships with the template (see its README.md), so do NOT run mkdir or ls to check - use the Read tool directly, and if Read returns "file does not exist", treat it as a first run and create the file with Write.
When you create the progress file for the first time, use this content (substitute today's date for YYYY-MM-DD):
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.
- 1mo ago First seen · 344 lines · 16 tokens per session scan A 0b80cfb29209
guide is a skill published in the GitHub repository aleksander-dytko/ai-pm-workspace (34 stars, last pushed 6mo ago), licensed MIT. It adds 16 tokens to every session and 4,975 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
explorer-interface-brief
Use when asked to design the interface for an interactive 3D explorer, plan a UI for exploring a 3D model of a topic, or write an image-model prompt for a 3D learning app mock-up. Produces, from a topic, the UI design brief (audience, layout, panels, interactions, label style, colour palette, accessibility) and an…
explorer-pipeline
Use when asked to make an interactive 3D explorer of a topic from start to finish, go from a topic to a clickable 3D learning page, or run the whole 3D explorer process. Produces a staged run of explorer-interface-brief, model-prompt-pack and explorer-viewer-builder in order for one topic, with the hand-offs between…
model-prompt-pack
Use when asked to write prompts for image-to-3D or text-to-3D tools, generate 3D models of a topic's parts, plan the assets for a 3D explorer, or build a labelled parts list with sources. Produces prompts for image-to-3D tools, one per object, plus a parts list for labelling in which every label names a trusted…
financial-statement-explainer
Explain a financial statement (P&L, balance sheet, or cash flow) in plain English. Use when asked to explain a P&L / income statement, a balance sheet, a cash flow statement, or to make financials understandable to a non-finance reader. Produces a plain-language walkthrough — what each section means, the line items…
get-more-from-ai
Level up how you actually use AI — from basic one-shot questions to the techniques that get dramatically better results — matched to what you already do. Use when asked how do I get better at using AI, how do power users use AI, I feel like I'm using AI at 10%, or teach me to use AI better. Produces an honest read of…
spot-ai-mistakes
Learn to recognize where and how AI tends to go wrong — the specific failure patterns — so you catch its mistakes on sight instead of getting burned by confident errors. Use when asked how do I know when AI is wrong, what are AI's common mistakes, how do I catch AI errors, or where does AI mess up. Produces the…