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 martinemde/dotfiles --skill project-managergit clone --depth 1 https://github.com/martinemde/dotfilesWrote 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/martinemde/dotfiles/project-manager)<a href="https://agentmods.dev/skills/martinemde/dotfiles/project-manager"><img src="https://agentmods.dev/badge/skills/martinemde/dotfiles/project-manager/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/martinemde/dotfiles/project-manager"><img src="https://agentmods.dev/badge/skills/martinemde/dotfiles/project-manager.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 109 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00038 | $0.00900 |
| Opus 5.5 | $0.00015 | $0.00360 |
| Sonnet 5.5 | $0.00008 | $0.00180 |
| Haiku 4.5 | $0.00004 | $0.00090 |
Grade A, and why
project-manager 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 8d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Manager
Write GitHub issues like a product manager. Focus on the user story, acceptance criteria, and context. Leave implementation notes when useful but never prescribe the solution.
Arguments
$ARGUMENTS
Instructions
1. Determine the Action
Parse arguments for intent:
createor a description with no issue number → create a new issueupdate #NNNor#NNNwith modification context → update an existing issuetriage→ review recent issues for gaps, duplicates, or missing context- Ambiguous → infer from conversation context; ask only if genuinely unclear
2. Learn the Repo's Voice
Before writing, fetch 3–5 recent issues from the same milestone (or repo if no milestone):
gh issue list --milestone "..." --json number,title,body --limit 5
Adapt to the conventions you observe:
- User story format ("As an X, I can Y") vs. problem/solution format
- Section headings (Use-case, Context, Acceptance criteria, Depends on, Future scope, etc.)
- Tone (terse vs. explanatory)
- Labeling and milestone conventions
If the repo has no issues yet, use a sensible default: user story + acceptance criteria + context.
3. Draft the Issue
Think like a PM, not an engineer:
- Title: Conventional commit prefix if the repo uses them. Concise — under 70 chars.
- User story or problem statement: Who benefits and what they can do. One sentence.
- Use-case: Numbered walkthrough of the happy path. 3–5 steps max.
- Context: Why this matters now. What's the alternative without it. What it builds on.
- Acceptance criteria: Observable behaviors, not implementation steps. Testable.
- Future scope: Things explicitly NOT in this issue. Reduces scope creep.
- Depends on: Link upstream issues. Use
#NNNformat. - Notes: Non-obvious constraints, gotchas, or pointers for whoever picks it up. Not a design doc.
What to leave out:
- File paths, function names, or code snippets (that's implementation)
- "How to build it" sections (let the implementer decide)
- Over-specified acceptance criteria that constrain the solution
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.
- 8d ago Changed · +38 tokens per session ded555ecf7de
- 1mo ago First seen · 117 lines · 0 tokens per session scan A 61a14e682cd8
project-manager is a skill published in the GitHub repository martinemde/dotfiles (10 stars, last pushed yesterday), licensed ISC. It adds 38 tokens to every session and 900 once invoked, about $0.0002 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-31.
Other skills, from other repositories
acli
Search, plan, and update Atlassian Jira and Confluence with acli.
github-issues
Plan, draft, update, link, and close GitHub issues.
podio-ticket-updates
Sync in-progress Podio Kanban tickets with progress from their linked GitHub repos — propose description updates and progress comments, apply after approval. Use when the user asks to update Podio tickets, sync ticket progress, or post status updates to the Kanban board.
align-readmes
Audit and converge README.md across every local urmzd/ checkout so the fleet reads as one product: skip archived repos, flag renamed repos and stale identities, score each README against write-readme, then fix in priority order. Use when the user asks to consolidate, unify, standardize, or audit READMEs across repos…
stakeholder-writing
Write reports, proposals, status updates, and executive summaries for busy readers, in HTML or Markdown.
bf
Search, read, and update Brain Framework brains (bf): project notes, decisions, actions, and collected mail, calendar, Git, chat, and agent-session records.