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 eveld/claude --skill discover-project-commandsgit clone --depth 1 https://github.com/eveld/claudeWrote 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/eveld/claude/discover-project-commands)<a href="https://agentmods.dev/skills/eveld/claude/discover-project-commands"><img src="https://agentmods.dev/badge/skills/eveld/claude/discover-project-commands/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/eveld/claude/discover-project-commands"><img src="https://agentmods.dev/badge/skills/eveld/claude/discover-project-commands.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.00028 | $0.00477 |
| Opus 5 | $0.00014 | $0.00238 |
| Sonnet 5 | $0.00006 | $0.00095 |
| Haiku 4.5 | $0.00003 | $0.00048 |
Grade A, and why
discover-project-commands 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 10d 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.
What it actually says
Discover Project Commands
Automatically discover and document all available commands in the project for reference during planning and implementation.
What to Discover
Make Targets
Check for Makefile and extract all targets:
- Use
make -qpor parse Makefile directly - Document target names and descriptions (from comments)
NPM Scripts
Check for package.json and extract scripts:
- Read package.json
- Document script names and what they do
Go Commands
If Go project, document standard commands:
go test ./...go build ./...go run- Custom test/build commands
Other Build Tools
Check for and document:
- Gradle tasks
- Maven goals
- Cargo commands
- Python setup.py commands
Output Format
Write to: thoughts/notes/commands.md
Use the template from templates/commands-reference.md and populate with discovered commands.
Discovery Process
- Check for Makefile: Parse targets and descriptions
- Check for package.json: Extract npm scripts
- Detect language: Look for go.mod, requirements.txt, Cargo.toml, etc.
- Document commands: Use template to create reference doc
- Include metadata: Add timestamp and project name
Example Output Structure
---
last_updated: 2025-12-23T10:00:00Z
last_updated_by: Claude
project: my-project
---
# Project Commands Reference
Last discovered: 2025-12-23
## Make Targets
- `make test` - Run all tests
- `make build` - Build the project
- `make lint` - Run linters
## NPM Scripts
- `npm test` - Run Jest tests
- `npm run build` - Build for production
## Common Verification Commands
- `make test` - Recommended for success criteria
- `make lint` - Recommended for code quality checks
When to Use
Automatically invoked by the plan command if thoughts/notes/commands.md doesn't exist.
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.
- 10d ago First seen · 83 lines · 28 tokens per session scan A 8586012e1273
discover-project-commands is a skill published in the GitHub repository eveld/claude (10 stars, last pushed 7mo ago), licensed MIT. It adds 28 tokens to every session and 477 once invoked, about $0.0001 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
ai-ml-development
AI and machine learning development with PyTorch, TensorFlow, and LLM integration. Use when building ML models, training pipelines, fine-tuning LLMs, or implementing AI features.
android-development
Android development with Kotlin, Jetpack Compose, and modern Android architecture. Use when building Android apps, implementing Material Design, or following Android best practices.
authentication-patterns
OAuth 2.0, JWT, SSO, MFA, NextAuth/Clerk/Supabase Auth implementation patterns.
email-systems
Transactional email (Resend, SendGrid, SES), templates (React Email, MJML), deliverability (SPF/DKIM/DMARC), and inboxing best practices. Use when building email infrastructure, designing templates, or troubleshooting deliverability.
customer-persona-builder
Data-driven customer persona development combining market research, user behavior analysis, and segmentation frameworks. Use when creating buyer personas, ideal customer profiles (ICPs), or user archetypes.
devops-cloud
DevOps, cloud infrastructure, and platform engineering. Use when working with AWS, GCP, Azure, Kubernetes, Terraform, CI/CD pipelines, or infrastructure as code.