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 dmythro/agent-skills --skill git-projectgit clone --depth 1 https://github.com/dmythro/agent-skillsWrote 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/dmythro/agent-skills/git-project)<a href="https://agentmods.dev/skills/dmythro/agent-skills/git-project"><img src="https://agentmods.dev/badge/skills/dmythro/agent-skills/git-project/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/dmythro/agent-skills/git-project"><img src="https://agentmods.dev/badge/skills/dmythro/agent-skills/git-project.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 153 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.00193 | $0.04679 |
| Opus 5.5 | $0.00077 | $0.01872 |
| Sonnet 5.5 | $0.00039 | $0.00936 |
| Haiku 4.5 | $0.00019 | $0.00468 |
Grade A, and why
git-project 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 19d 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Project Management
Primary skill for organizing a repository's issues into an epic-based roadmap on a GitHub Project (v2) and running the day-to-day on it. Covers setup (project, fields, views, native workflows) and operations (create epics with sub-issues, drive Status, move work, prioritize). GitHub-only, via gh project + gh api (REST sub-issues + GraphQL).
Verified against gh v2.102.0 (2026-09-30): every gh subcommand and flag used here, against its --help. Minimums are tagged where they matter (gh >= 2.94, >= 2.97). If gh --version is newer, read the release notes since v2.102.0 for gh project and gh issue changes before relying on flag details.
The conventions here are non-obvious and easy to get half-right: the UI nests issues by native parent/child links and tracks progress on a separate board Status field -- neither of which a markdown checklist or a closed issue touches. Get those two wrong and the work looks done while the structure silently drifts. This skill makes the flow correct-by-default.
When to Use
- Setting up a project/roadmap -- create the Project, fields (Status, Priority), the Epic + Upcoming views, enable native workflows
- Creating an epic with issues -- "make an epic X with these issues", "group these under an epic"
- Filing / moving work -- attach an issue under an epic, move an issue between epics, add new work
- Driving the board -- pick up an issue (-> In Progress), close one (-> Done), (re)prioritize
- Classifying work -- set native issue Types (Task/Bug/Feature) instead of type labels
- Milestone scoping -- create a milestone for a deliverable, assign issues, close it out; resolve "current milestone" / "milestone N"
- Migrating an existing repo's loose issues into this structure
- Granting access -- a teammate cannot apply labels, assign, link sub-issues, or edit Status/Priority
- Configuring tool allowlists -- auto-approval patterns for read-only
gh projectcommands
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 19d ago Changed · +3 lines b0a1062ab905
- 1mo ago Changed · +21 lines · +17 tokens per session fbd70185821b
- 1mo ago First seen · 168 lines · 176 tokens per session scan A 5ba69e827a43
git-project is a skill published in the GitHub repository dmythro/agent-skills (7 stars, last pushed 10d ago), licensed MIT. It adds 193 tokens to every session and 4,679 once invoked, about $0.0008 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
project-planner
Converts an idea into a structured development plan with milestones, tasks, dependencies, and implementation phases. Use when an idea or feature needs to be broken into a plan before work starts.
commit-message-expert
Generates consistent, meaningful Git commit messages based on a diff or description of changes. Use when writing or reviewing a commit message, especially to follow Conventional Commits or a project's existing convention.
retro-facilitator
Structures raw sprint retro notes into themes and concrete actions. Use after a retro when raw sticky-note-style input (what went well/poorly/to try) needs to become a clean summary with follow-through.
incident-postmortem-writer
Structures raw incident notes into a blameless postmortem - timeline, root cause, impact, and action items. Use after an incident/outage once the immediate fire is out and it needs to be documented.
secrets-scanner
Narrowly scans code and config for hardcoded secrets, credentials, API keys, and tokens. Use before a commit/PR, or when auditing a codebase for accidentally-committed secrets.
changelog-generator
Converts commits or development updates into clean, categorized release notes and changelogs. Use when preparing a release and raw commit history needs to become human-readable notes.