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 sjarmak/coding-agent-workflows --skill coding-practicesgit clone --depth 1 https://github.com/sjarmak/coding-agent-workflowsWrote 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/sjarmak/coding-agent-workflows/coding-practices)<a href="https://agentmods.dev/skills/sjarmak/coding-agent-workflows/coding-practices"><img src="https://agentmods.dev/badge/skills/sjarmak/coding-agent-workflows/coding-practices/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/sjarmak/coding-agent-workflows/coding-practices"><img src="https://agentmods.dev/badge/skills/sjarmak/coding-agent-workflows/coding-practices.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.00114 | $0.00486 |
| Opus 5.5 | $0.00046 | $0.00194 |
| Sonnet 5.5 | $0.00023 | $0.00097 |
| Haiku 4.5 | $0.00011 | $0.00049 |
Grade A, and why
coding-practices 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 16d 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
Coding Practices Index
The always-on essentials load every session from
.claude/rules/common/house-rules.md (autonomy boundary, output discipline,
coding/architecture/security standards, ZFC, the anti-slop trigger). The full
per-topic detail is not auto-loaded — it ships under .claude/rules-reference/
(common topics) and .claude/rules/<lang>/ (language rules) to keep the context
window lean. Read the one rule relevant to your current task, when you need it.
This skill is the catalog of that on-demand detail.
How to use
- Match your task to a rule in the catalog below — e.g. touching a task tracker →
task-management; extending existing code →anti-slop; adding an endpoint or a migration →securityplus the language rule. - Read that file with your file tool. Read only the rule you need.
- Apply it, and re-read on demand. Don't pull the whole rulebook into context.
Rule catalog
Notes
- Paths are relative to the installed
.claude/directory (~/.claude/for a user-level install). - AGENTS.md-based agents (Codex, Amp, Aider, …) get the same on-demand shape from
the thin
AGENTS.mdindex overAGENTS.full.md; this skill is the Claude Code equivalent for the rules shipped under.claude/rules/.
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.
- 16d ago Changed 77d0b3767ee1
- 1mo ago First seen · 38 lines · 114 tokens per session scan A b699fd9434e6
coding-practices is a skill published in the GitHub repository sjarmak/coding-agent-workflows (6 stars, last pushed 17d ago), licensed MIT. It adds 114 tokens to every session and 486 once invoked, about $0.0005 per session on Opus 5.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
browser-trace
Capture a full DevTools-protocol trace of any browser automation — CDP firehose, screenshots, and DOM dumps — then bisect the stream into per-page searchable buckets. Use when the user wants to debug a failed run, audit network/console/DOM activity, attach a trace to an in-progress session, or feed structured per-page…
planning-with-files
Persistent file-based planning for multi-step AI-agent work. Keeps taskplan.md, findings.md, and progress.md on disk; lifecycle hooks inject selected project planning context. Automatic recovery reads project planning files only. Explicit session-catchup.py --metadata reads same-project local agent session records and…
ai-elements
Build AI chat interfaces using ai-elements components — conversations, messages, tool displays, prompt inputs, and more. Use when the user wants to build a chatbot, AI assistant UI, or any AI-powered chat interface.
exa-search
Use Exa MCP for current web, code/docs, company, people, and page-fetch research. Prefer current hosted tool schemas and note deprecated tools.
ontoly-software-graph
Use Ontoly's deterministic Software Graph and MCP capabilities for repository architecture, request tracing, dependency analysis, configuration lookup, and impact analysis before falling back to source search.
kimi-webbridge
A way for an AI agent to control the user's real web browser, including pages where the user is already signed in. It can navigate, click, type, read page content, and take screenshots.