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 avmnu-sng/sutra --skill style-auditgit clone --depth 1 https://github.com/avmnu-sng/sutraWrote 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/avmnu-sng/sutra/style-audit)<a href="https://agentmods.dev/skills/avmnu-sng/sutra/style-audit"><img src="https://agentmods.dev/badge/skills/avmnu-sng/sutra/style-audit/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/avmnu-sng/sutra/style-audit"><img src="https://agentmods.dev/badge/skills/avmnu-sng/sutra/style-audit.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.00050 | $0.01616 |
| Opus 5 | $0.00025 | $0.00808 |
| Sonnet 5 | $0.00010 | $0.00323 |
| Haiku 4.5 | $0.00005 | $0.00162 |
Grade A, and why
style-audit 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 9d 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Style audit
A field guide to the code and documentation house style, plus a procedure for auditing a change against it. Run this before you consider a diff done, or when reviewing someone else's diff.
When to use
- Finishing a change that touches source comments, docs, or diagrams.
- Reviewing a pull request for style, not just correctness.
- Writing a new doc and deciding what belongs in it.
When not to
- Mechanical, generated, or vendored files you do not own.
- A pure logic change with no comments, docs, or prose touched -- run your normal correctness review instead.
The rules
1. Files are ASCII-only when the project's style calls for it
This rule applies only when the project enforces ASCII -- sutra's strict
profile (SUTRA_PROFILE=strict) does. If the project does not enforce
ASCII, skip this rule and let its own encoding conventions stand.
-
No non-ASCII bytes anywhere in a committed text file.
-
Write
--for an em dash,->for an arrow, and straight quotes ('and") instead of curly ones. -
If a sentence seems to need a special character, rewrite the sentence. There is always an ASCII phrasing.
-
Verify, do not eyeball. Run the
filecommand and confirm it reportsASCII text:file path/to/changed_fileIf it reports
UTF-8 textor names another encoding, a non-ASCII byte slipped in. Find it and fix it. To locate offending bytes:grep -nP '[^\x00-\x7F]' path/to/changed_file
Common leaks: pasted smart quotes, a real em dash or en dash, a Unicode arrow, non-breaking spaces, and accented characters copied from a browser.
2. Comments explain WHY, not WHAT
- Comment only where the logic is non-obvious -- an external constraint, a workaround, a non-local invariant, a deliberate deviation.
- Delete any comment whose removal loses no information. A comment that restates the code it sits above is noise.
- Prefer self-documenting code: a clear name beats a comment that explains an unclear one.
- Good: "Retry cap is 3 because the upstream event service rejects a fourth attempt within the same minute." Bad: "increment the counter."
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.
- 9d ago First seen · 157 lines · 50 tokens per session scan A 2e18f3391e5f
style-audit is a skill published in the GitHub repository avmnu-sng/sutra (2 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 1,616 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
memstack-development-code-reviewer
Use this skill when the user says 'review code', 'code review', 'check my code', 'audit this', 'review PR', 'review changes', 'what's wrong with this', or is requesting a structured review of code quality, security, performance, or maintainability. Do NOT use for refactoring plans or test generation.
shard
Use when the user says 'shard this', 'split file', or when working with files over 1000 lines.
audit-agents-skills
Audit Claude Code agents, skills, and commands for quality and production readiness. Use when evaluating skill quality, checking production readiness scores, or comparing agents against best-practice templates.
design-patterns
Detect, suggest, and evaluate GoF design patterns in TypeScript/JavaScript codebases. Use when refactoring code, applying singleton/factory/observer/strategy patterns, reviewing pattern quality, or finding stack-native alternatives for React, Angular, NestJS, and Vue.
pr-triage
4-phase PR backlog management with audit, deep code review, validated comments, and optional worktree setup. Use when triaging pull requests, catching up on pending code reviews, or managing a backlog of open PRs. Args: 'all' to review all, PR numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit…
eval-skills
Audit all skills in the current project for frontmatter completeness, effort level appropriateness, allowed-tools scoping, and content quality. Produces a scored report with effort-level recommendations for each skill. Use when onboarding to a new project, reviewing skill quality before shipping, or adding effort…