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/arogyareddy/https-github.com-affaan-m-everything-claude-code1/add-language-rulesgit clone --depth 1 https://github.com/ArogyaReddy/https-github.com-affaan-m-everything-claude-code1What 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.00020 | $0.00274 |
| Opus 5 | $0.00010 | $0.00137 |
| Sonnet 5 | $0.00004 | $0.00055 |
| Haiku 4.5 | $0.00002 | $0.00027 |
Grade A, and why
add-language-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 yesterday.
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.
This is a copy
100% identical to add-language-rules — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
/add-language-rules
Use this workflow when working on add-language-rules in everything-claude-code.
Goal
Adds a new programming language to the rules system, including coding style, hooks, patterns, security, and testing guidelines.
Common Files
rules/*/coding-style.mdrules/*/hooks.mdrules/*/patterns.mdrules/*/security.mdrules/*/testing.md
Suggested Sequence
- Understand the current state and failure mode before editing.
- Make the smallest coherent change that satisfies the workflow goal.
- Run the most relevant verification for touched files.
- Summarize what changed and what still needs review.
Typical Commit Signals
- Create a new directory under rules/{language}/
- Add coding-style.md, hooks.md, patterns.md, security.md, and testing.md files with language-specific content
- Optionally reference or link to related skills
Notes
- Treat this as a scaffold, not a hard-coded script.
- Update the command if the workflow evolves materially.
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.
- yesterday First seen · 39 lines · 20 tokens per session scan A 9c2a0c46e0ac
add-language-rules is a command published in the GitHub repository ArogyaReddy/https-github.com-affaan-m-everything-claude-code1 (2 stars, last pushed 4mo ago), licensed MIT. It adds 20 tokens to every session and 274 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to add-language-rules, differing in 2 lines, and is treated as a copy.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.