Borrowing it
Nothing to install: this file belongs to fabioc-aloha/Alex_Skill_Mall. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/fabioc-aloha/Alex_Skill_Mall/main/.github/instructions/severity-tagged-commits.instructions.mdgit clone --depth 1 https://github.com/fabioc-aloha/Alex_Skill_MallWrote 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/instructions/fabioc-aloha/alex_skill_mall/severity-tagged-commits)<a href="https://agentmods.dev/instructions/fabioc-aloha/alex_skill_mall/severity-tagged-commits"><img src="https://agentmods.dev/badge/instructions/fabioc-aloha/alex_skill_mall/severity-tagged-commits/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/instructions/fabioc-aloha/alex_skill_mall/severity-tagged-commits"><img src="https://agentmods.dev/badge/instructions/fabioc-aloha/alex_skill_mall/severity-tagged-commits.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.01630 | $0.01630 |
| Opus 5 | $0.00815 | $0.00815 |
| Sonnet 5 | $0.00326 | $0.00326 |
| Haiku 4.5 | $0.00163 | $0.00163 |
Grade A, and why
Alex_Skill_Mall severity-tagged-commits.instructions.md 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 12d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Severity-tagged brain edits
Every commit that touches a brain artefact must carry a severity tag. The tag determines the level of pre-commit scrutiny required and restores credit-assignment fidelity that flat commit lists destroy — without tags, a typo fix and a constitutional rule change have identical weight in git log.
The four tiers
| Tier | When to use | ACT-pass required? | Examples |
|---|---|---|---|
[typo] |
Pure typo, formatting, spelling, link fix. No content semantics change. | No | "fix typo in skill description", "wrap long line", "repair broken markdown link" |
[clarification] |
Wording change that sharpens an existing rule without changing what it does. | No | "rephrase ambiguous instruction", "add example to clarify existing rule", "expand acronym on first use" |
[behaviour] |
Changes what the AI does — adds a new rule, modifies an existing trigger, introduces a new skill / prompt / muscle / instruction. | Yes (trimmed pass minimum, per act-pass.instructions.md) | "add brain-review trigger condition", "new meditation skill", "lower default temperature" |
[constitutional] |
Changes a rule that other rules depend on — governance, hard floors, the ACT framework itself, Cardinal Rules, severity-tag rules. | Yes (full pass; visible markers in commit message body) | "broaden whole-plan kill criterion", "rebrand identity", "promote Mall plugin to bundled tier", "fleet-wide policy change" |
Where the tag goes
In the commit subject line, first thing after any conventional-commits prefix:
[typo] fix broken link in append-and-review/SKILL.md
[clarification] sharpen Phase 1 deliverables checklist in PLAN.md
[behaviour] add severity-tagged-commits always-on instruction
[constitutional] broaden whole-plan kill criterion to permit any premise-undermining finding
Conventional-commits style (feat:, fix:, docs:) is optional — the severity tag is the load-bearing element. If using both:
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.
- 12d ago First seen · 105 lines · 1,630 tokens per session scan A 0cbc0af1ba0c
Alex_Skill_Mall severity-tagged-commits.instructions.md is an instructions file published in the GitHub repository fabioc-aloha/Alex_Skill_Mall (4 stars, last pushed yesterday), licensed MIT. It adds 1,630 tokens to every session, about $0.0081 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 instructions, from other repositories
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).