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 commands/sgaunet/claude-plugins/gen-taskfilesgit clone --depth 1 https://github.com/sgaunet/claude-pluginsWhat 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.00032 | $0.05763 |
| Opus 5 | $0.00016 | $0.02882 |
| Sonnet 5 | $0.00006 | $0.01153 |
| Haiku 4.5 | $0.00003 | $0.00576 |
Grade C, and why
gen-taskfiles scanned grade C with 2 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
machine (`brew install mise`, or `curl https://mise.run | sh` — Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
machine (`brew install mise`, or `curl https://mise.run | sh` — How it starts
The opening of the file, as written. The whole thing — 640 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Taskfiles Command
Instantly create a complete Task automation setup for Go projects including a mise.toml (development tool versions), the main Taskfile, development tasks, and pre-commit hooks configuration. This command provides a comprehensive task runner setup with linting, testing, building, and release automation — and pins the tool versions so local development and CI stay in sync.
Why This Command Exists
Problem: Setting up task automation for Go projects requires manually creating Taskfile configuration, understanding Task syntax, pinning tool versions, and configuring pre-commit hooks - a 20-30 minute process.
Solution: One-command generation that:
- Creates complete dev setup (4 files):
mise.toml,Taskfile.yml,Taskfile_dev.yml,.pre-commit-config.yaml - Pins tool versions in
mise.toml(go, task, golangci-lint, goreleaser) so local dev and CI use identical versions - Includes tasks: lint, test, build, snapshot, release, image, doc
- Configures pre-commit hooks for automated quality checks
- Integrates with golangci-lint and goreleaser
mise.toml is the single source of truth for tool versions. It is consumed by the CI generators (/gen-github-dir, /gen-forgejo-dir, /gen-gitlab-ci), whose workflows install tools via mise and then run task …. See https://mise.jdx.dev.
Content Generation Rules
CRITICAL: When generating any content (taskfiles, commit messages, or any other output):
- NEVER add Claude Code attribution or co-authorship
- NEVER include phrases like "Generated by Claude", "Created with Claude Code", or similar
- NEVER add "Co-Authored-By: Claude" in commit messages or documentation
- All generated content should appear as if written by a human developer
- Focus on technical accuracy and providing working templates
Process (6 Phases)
Phase 1: Prerequisites Validation
Critical checks before proceeding:
- Validate Git repository:
git rev-parse --git-dir- If fails: Exit with error "Not a git repository. Run 'git init' first."
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 · 640 lines · 32 tokens per session scan C e874044a980a
gen-taskfiles is a command published in the GitHub repository sgaunet/claude-plugins (16 stars, last pushed 7d ago), licensed MIT. It adds 32 tokens to every session and 5,763 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
security-audit-static
Static security audit of AI-built code — map trust boundaries, cross-reference documented intent, self-refute every finding, and report only evidence-backed risks.
performance-audit-static
Static performance audit of AI-built code — find N+1 queries and request waterfalls, over-fetching, missing indexes, and caching opportunities, ranked by effort and impact.
sprint
Sprint lifecycle — plan a sprint, run a retrospective, or generate release notes.
document-app
Reverse-engineer an AI-built codebase into the system documents reviewers and auditors need — a core set (architecture, flows, permissions, variables) plus conditional docs (emails, cron, SEO, automation) when they apply.
analyze-test
Analyze A/B test results — statistical significance, sample size validation, and ship/extend/stop recommendations.
plan-okrs
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results.