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/bodangren/git-workflow/skill-listernpx skills add bodangren/git-workflow --skill skill-listergit clone --depth 1 https://github.com/bodangren/git-workflowWrote 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/bodangren/git-workflow/skill-lister)<a href="https://agentmods.dev/skills/bodangren/git-workflow/skill-lister"><img src="https://agentmods.dev/badge/skills/bodangren/git-workflow/skill-lister.svg" alt="Measured on agentmods" 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 | $0.00047 | $0.00963 |
| Opus 5 | $0.00023 | $0.00481 |
| Sonnet 5 | $0.00009 | $0.00193 |
| Haiku 4.5 | $0.00005 | $0.00096 |
Grade B, and why
skill-lister scanned grade B with 1 finding 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 3d 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.
Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
- Check directory permissions: `ls -la .claude/skills/` How it starts
The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Lister
Purpose
Provide a comprehensive overview of all available AgenticDev skills in the project. The skill-lister scans the .claude/skills/ directory, extracts skill metadata from SKILL.md files, and returns a formatted list of all discovered skills with their descriptions and script paths. This enables AI agents to quickly understand what capabilities are available without manually exploring the directory structure.
When to Use
Use this skill in the following situations:
- At the beginning of any work session to understand available AgenticDev capabilities
- When onboarding to a new project using AgenticDev
- Before deciding which skill to use for a particular task
- When documenting or auditing the project's AgenticDev setup
- To verify that all expected skills are installed and accessible
Prerequisites
- The project must have a
.claude/skills/directory - Skills should follow the convention of including SKILL.md files with YAML frontmatter
- No additional tools required (pure bash implementation)
Workflow
Step 1: Run the Skill Lister
Execute the helper script to scan all skills in the .claude/skills/ directory:
bash .claude/skills/skill-lister/scripts/list-skills.sh
This will output a human-readable summary showing each skill's metadata including:
- Skill name
- Description
- Available scripts
For machine-readable JSON output (useful for programmatic processing):
bash .claude/skills/skill-lister/scripts/list-skills.sh -j
Step 2: Review the Skills List
The scanner returns information about all skills found in .claude/skills/, including:
- Skill name: The identifier for the skill (from YAML frontmatter)
- Description: What the skill does and when to use it
- Script paths: All executable scripts available for the skill
- Directory: Location of the skill in the filesystem
Step 3: Choose the Appropriate Skill
Based on the output, select the skill that best matches your current task:
What ships with it
1 file 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.
- 3d ago First seen · 115 lines · 47 tokens per session scan B 018418e2594f
skill-lister is a skill published in the GitHub repository bodangren/git-workflow (11 stars, last pushed 9mo ago), licensed MIT. It adds 47 tokens to every session and 963 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…