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 tommyvo/useful-prompts --skill generate-gitignoregit clone --depth 1 https://github.com/tommyvo/useful-promptsWrote 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/tommyvo/useful-prompts/generate-gitignore)<a href="https://agentmods.dev/skills/tommyvo/useful-prompts/generate-gitignore"><img src="https://agentmods.dev/badge/skills/tommyvo/useful-prompts/generate-gitignore/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/tommyvo/useful-prompts/generate-gitignore"><img src="https://agentmods.dev/badge/skills/tommyvo/useful-prompts/generate-gitignore.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.00026 | $0.00616 |
| Opus 5 | $0.00013 | $0.00308 |
| Sonnet 5 | $0.00005 | $0.00123 |
| Haiku 4.5 | $0.00003 | $0.00062 |
Grade A, and why
generate-gitignore 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.
How it starts
The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate .gitignore File
Goal
Create a comprehensive .gitignore file at the root of the project that covers common development environments, frameworks, and operating systems.
Process
- CRITICAL: Check if
.gitignorealready exists at project root - If exists, ask user to confirm overwrite
- Write
.gitignorewith the comprehensive template - Confirm file creation
Instructions
Step 1: Check Existing File
If .gitignore exists at project root, ask user: "A .gitignore file already exists. Overwrite it? (yes/no)"
If user says no, abort operation.
Step 2: Create .gitignore File
Write this exact template to .gitignore at project root:
# VS Code
.vscode/*
!.vscode/settings.json
!.vscode/tasks.json
!.vscode/launch.json
!.vscode/extensions.json
*.code-workspace
# JetBrains IDEs (IntelliJ, RubyMine, WebStorm, etc.)
.idea/
*.iml
*.iws
*.ipr
out/
# Rails
*.rbc
capybara-*.html
.rspec
/log/*
/tmp/*
!/log/.keep
!/tmp/.keep
/db/*.sqlite3
/db/*.sqlite3-journal
/db/*.sqlite3-*
/public/system
/coverage/
/spec/tmp
*.orig
rerun.txt
pickle-email-*.html
.byebug_history
/config/master.key
/config/credentials/*.key
# React / Node.js
node_modules/
npm-debug.log*
yarn-debug.log*
yarn-error.log*
.pnp.*
.yarn/*
!.yarn/patches
!.yarn/plugins
!.yarn/releases
!.yarn/versions
build/
dist/
.env.local
.env.development.local
.env.test.local
.env.production.local
# Worktrees
worktrees/
# DevOps / Infrastructure
*.tfstate
*.tfstate.*
.terraform/
.terragrunt-cache/
*.pem
*.key
.envrc
.vagrant/
# Environment variables
.env
.env.*
!.env.example
# Logs
*.log
logs/
# OS - macOS
.DS_Store
.AppleDouble
.LSOverride
._*
# OS - Windows
Thumbs.db
ehthumbs.db
Desktop.ini
# OS - Linux
*~
.fuse_hidden*
.directory
.Trash-*
.nfs*
Step 3: Confirm Creation
Output a simple confirmation message:
✅ Created .gitignore at project root
File: [absolute path to .gitignore]
Output Format
Write directly to .gitignore file at project root. Provide confirmation message in chat only.
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 · 137 lines · 26 tokens per session scan A 1c36ee548f1e
generate-gitignore is a skill published in the GitHub repository tommyvo/useful-prompts (3 stars, last pushed 13d ago), licensed Unlicense. It adds 26 tokens to every session and 616 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
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.