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 Sagargupta16/claude-skills --skill dev-rulesgit clone --depth 1 https://github.com/Sagargupta16/claude-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/sagargupta16/claude-skills/dev-rules)<a href="https://agentmods.dev/skills/sagargupta16/claude-skills/dev-rules"><img src="https://agentmods.dev/badge/skills/sagargupta16/claude-skills/dev-rules.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.1 | $0.00052 | $0.01079 |
| Opus 5 | $0.00026 | $0.00540 |
| Sonnet 5 | $0.00010 | $0.00216 |
| Haiku 4.5 | $0.00005 | $0.00108 |
Grade A, and why
dev-rules 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 8d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Development Rules and Guardrails
Git Safety
| Rule | Why |
|---|---|
| Never force push to main/master | Destroys team history, breaks CI |
Never git reset --hard without confirmation |
Irreversible data loss |
| Never amend published commits | Creates divergent history for collaborators |
Never skip pre-commit hooks (--no-verify) |
Hooks catch real issues |
| Stage specific files by name | git add . risks committing secrets or binaries |
| Never commit .env, credentials, API keys | Secrets in git history are permanent |
| Verify current branch before pushing | Avoid pushing to wrong branch |
Security
Secrets and Credentials
- Never commit
.envfiles, API keys, tokens, passwords, or connection strings - Always use
.env.examplewith placeholder values, never real credentials - If real credentials are found in git history, flag immediately - they must be rotated
- Add secret config files to
.gitignore(e.g.,config/secrets.yml)
Code Security
- Validate all user input at system boundaries (API endpoints, form submissions)
- Use parameterized queries - never string concatenation for database queries
- Sanitize data before rendering in templates (prevent XSS)
- Use bcrypt or argon2 for password hashing, never MD5 or SHA for passwords
- Set CORS origins from environment variables, never wildcard in production
Dependency Security
- Check for known vulnerabilities before adding new packages
- Prefer well-maintained packages with active security response
- Pin dependency versions in lock files
PR Workflow
When working with pull requests:
- Always read comments first before making changes
gh api repos/{owner}/{repo}/issues/{num}/commentsgh api repos/{owner}/{repo}/pulls/{num}/comments
- Check merge readiness before acting
gh api repos/{owner}/{repo}/pulls/{num} --jq '{mergeable, mergeable_state, draft}'
- Check how far behind the base branch
gh api repos/{owner}/{repo}/compare/{base}...{head} --jq '{behind_by, ahead_by}'
- After fixing/rebasing your own repo's PR - comment a summary of what was done. On upstream or fork PRs, never comment without the user's or maintainer's explicit go-ahead
- Before deleting a fork - verify zero open PRs from that fork
- When rebasing - squash into clean commits, match project's commit style
- Never force-push to someone else's branch - only to your own fork branches
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.
- 8d ago First seen · 100 lines · 52 tokens per session scan A 8ac3beaa4d30
dev-rules is a skill published in the GitHub repository Sagargupta16/claude-skills (5 stars, last pushed yesterday), licensed MIT. It adds 52 tokens to every session and 1,079 once invoked, about $0.0003 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
release
This skill should be used when the user wants to create a new release — bump version, tag, push, create GitHub release, and optionally publish to npm. Use when user says "release", "bump version", "publish", "cut a release", or "release candidate".
crafting-commits
Generates git commit messages following conventional commit standards with collaborative attribution. Use when user requests commit message creation, drafting, or help with formatting.
branch-hygiene
Classify and clean up merged, stale, and orphaned git branches and worktrees. Detects squash-merges that git branch --merged cannot see, stale worktrees, and remote-gone branches. Use when user asks to clean up branches, prune worktrees, tidy the repo, or perform git housekeeping.
changelog-summarizing
Use this skill when the user asks to summarize, recap, or post about repository changes in the Shopware AI Coding Tools marketplace since a given date — phrases like "write a changelog post for Discord", "recap this week's commits for Slack", "summarize what shipped since 2026-04-01", "draft a release announcement".…
commit-message-writing
Use this skill when the user explicitly asks to generate, write, draft, or create a commit message, squash commit, commit title, or merge commit message for the Shopware core repository (shopware/shopware). Supports two modes — full commit messages (title + body) for branch commits, and squash merge titles…
plugin-updating
Use this skill when the user asks to bump, update, or release a new version of a plugin in the Shopware AI Coding Tools marketplace — phrases like "bump test-writing to 3.8.0", "release a patch for dev-tooling", "update the plugin version". Handles synchronized version bumps across plugin.json and every SKILL.md…