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 reportgit 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/report)<a href="https://agentmods.dev/skills/aleksander-dytko/ai-pm-workspace/report"><img src="https://agentmods.dev/badge/skills/aleksander-dytko/ai-pm-workspace/report/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/report"><img src="https://agentmods.dev/badge/skills/aleksander-dytko/ai-pm-workspace/report.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.00022 | $0.01149 |
| Opus 5.5 | $0.00009 | $0.00460 |
| Sonnet 5.5 | $0.00004 | $0.00230 |
| Haiku 4.5 | $0.00002 | $0.00115 |
Grade A, and why
report 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Report
You help the user submit feedback about the template to the upstream repo as a GitHub issue. Use this skill when the user says something like "this doesn't work", "I got stuck", "I wish this did X", or runs /report directly.
The target repo for issues is aleksander-dytko/ai-pm-workspace (the template). Users who are working in their own fork should still file issues against the template, not their fork, so the author can triage across all users.
Input
The user may provide via $ARGUMENTS:
- A short description of the issue.
- Nothing (skill will prompt).
Workflow
1. Categorize the feedback
Ask in one AskUserQuestion (unless the category is obvious from the argument):
- Category:
- Bug - something broke or produced wrong output
- Confusion - I got stuck or couldn't figure out how to do something
- Feature request - I want the template to do something it doesn't
- Other feedback - appreciation, context, observation
2. Collect context
Prompt for:
- What happened / what you wanted: free text, 2-3 sentences.
- Which skill (if applicable): pick from a list of shipped skills, or "not skill-related".
- What you expected vs. what happened (for Bug / Confusion only).
Skip any field the user already provided in $ARGUMENTS.
3. Check if GitHub MCP is available
Look at the deferred tools list (or the MCP Servers Available section in CLAUDE.md). If any mcp__github__* tools are present, GitHub MCP is available.
4a. If GitHub MCP is available: open the issue directly
Use the GitHub MCP issue-creation tool with:
- Repo:
aleksander-dytko/ai-pm-workspace - Title:
[{Category}] {short description}. Example:[Bug] /meeting crashes when meeting note has no attendees. - Body: use this template
## Category
{Bug | Confusion | Feature request | Other}
## What happened / what I wanted
{User's description}
## Which skill (if any)
{skill name or "not skill-related"}
## Expected vs. actual (bug / confusion only)
**Expected**: {user's expected outcome}
**Actual**: {what actually happened}
## Environment
- Template version / commit: {try to read from CHANGELOG.md top header; fallback "v2"}
- Claude Code version: {ask user if unknown}
- OS: {ask or infer}
---
Submitted via `/report` skill.
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 · 127 lines · 22 tokens per session scan A 7630b46da057
report is a skill published in the GitHub repository aleksander-dytko/ai-pm-workspace (34 stars, last pushed 6mo ago), licensed MIT. It adds 22 tokens to every session and 1,149 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
feature-prioritisation
Aplica marcos de priorización (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) para clasificar características e items del backlog. Úsalo cuando se te pida priorizar características, clasificar un backlog, decidir qué construir a continuación, o evaluar compensaciones entre ideas competidoras. Produce una lista de…
morning-intelligence
Interviews you across 15 questions to capture your role, topics, sources, exclusions, and format preferences, then writes a master prompt you can paste into a scheduled task or Claude Code Routine. Use when you want to set up a personalised daily news brief, build a reusable morning news prompt, or create an automated…
technical-spec-template
Crea documentos de especificación técnica estructurados que conectan requisitos de producto con implementación de ingeniería. Úsalo cuando escribas una especificación técnica, especificación de ingeniería, documento de diseño de sistema o especificación de API. Produce una especificación completa con declaración del…
design-handoff-brief
Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context…
outcome-tracker
Record the testable predictions inside a decision, then score them against reality later — so frameworks earn trust from outcomes, not vibes. Use when committing to a prioritisation, forecast, or plan (to log what it predicts), when asked to review what actually happened, or to compute how well-calibrated past RICE…
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…