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 agentmods add skills/martinemde/dotfiles/project-managernpx skills add martinemde/dotfiles --skill project-managergit clone --depth 1 https://github.com/martinemde/dotfilesWhat 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 | $0.00038 | $0.00921 |
| Opus 5 | $0.00019 | $0.00461 |
| Sonnet 5 | $0.00008 | $0.00184 |
| Haiku 4.5 | $0.00004 | $0.00092 |
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 2d 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.
- 2d ago First seen · 117 lines · 0 tokens per session scan A 61a14e682cd8
project-manager is a skill published in the GitHub repository martinemde/dotfiles (9 stars, last pushed 1mo ago), licensed ISC. It adds 38 tokens to every session and 921 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-31.
Other skills, from other repositories
dotfiles-bootstrap
Bootstrap a workstation with the dotfiles framework. Takes a GitHub user / owner+repo / explicit clone URL and runs dot init (which shells out to chezmoi) with the right safety prompts. Honors the active agent profile (ask / plan / apply / audit) so it defaults to dry-run in safer modes and full apply in apply.
vibe
Delegate a coding task to a cheap AI model (Mistral Vibe by default, but any provider Vibe knows about — DeepSeek, Gemini Flash, etc.) and supervise the result via git diff. Claude orchestrates, the cheap model codes. Claude consumes 500-1500 tokens per delegation regardless of how many file reads the delegate does…
aiq-research
Use when asked to run deep research or AI-Q research through a reachable NVIDIA AI-Q Blueprint backend.
obsidian-bases
Obsidian Bases database feature for YAML-based interactive note views. Use when creating .base files, writing filter queries, building formulas, configuring table/card views, or working with Obsidian properties and frontmatter databases.
telegram
Send notifications, interactive questions, or multiple-choice polls to the user via Telegram. Use when the user asks to be notified ("ping me", "notify me on Telegram", "ask me when..."), when a long-running task finishes and the user is likely away, when an irreversible action needs out-of-band confirmation, or when…
chezmoi-expert
Comprehensive chezmoi dotfiles management expertise including templates, cross-platform configuration, file naming conventions, and troubleshooting. Covers source directory management, reproducible environment setup, and chezmoi templating with Go templates. Use when user mentions chezmoi, dotfiles, cross-platform…