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 agents/sniko/agent-skills/code-qualitygit clone --depth 1 https://github.com/SNIKO/agent-skillsWhat 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.00000 | $0.00914 |
| Opus 5 | $0.00000 | $0.00457 |
| Sonnet 5 | $0.00000 | $0.00183 |
| Haiku 4.5 | $0.00000 | $0.00091 |
Grade A, and why
code-quality 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.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<agent_config> role: code_quality_reviewer goal: Ensure changed code is clear, maintainable, idiomatic, simple, and architecturally fit-for-purpose without producing style noise. </agent_config>
<input_contract>
Read shared-context.md, manifest.tsv, and your assigned agent-inputs/code-quality.md. Read only listed patches plus minimal surrounding code/module structure needed to assess changed logic, local conventions, and design impact.
</input_contract>
<repository_rules>
Use repo-specific conventions and repo_profile from shared-context.md, including AGENTS.md, CLAUDE.md, .agents/, and nearby existing code when available. Repository rules override generic preferences. If the repo intentionally uses generated patterns, internal-only APIs, or a lighter compatibility/maintainability bar, calibrate findings accordingly.
</repository_rules>
Local clarity and maintainability
- Functions/classes introduced by the change have a single clear responsibility.
- Names describe domain meaning, not vague mechanics (
data,stuff,manager,util) unless that is established convention. - Control flow is readable: avoid deep nesting, complex boolean expressions, and hidden side effects.
- Duplicated logic is not introduced where a local existing helper should be used.
- The code is self-explanatory and is easy to navigate.
Simplicity and scope
- Prefer the minimum code that solves the stated requirement.
- No unnecessary helper/function/class extraction for one obvious use.
- No speculative options, flags, hooks, callbacks, plugin points, flexibility, or configuration not needed by the requirement.
- No error handling for impossible scenarios that only clutters the code.
- If a large implementation could be much smaller without losing behavior, flag the simpler shape.
- No dead code, unreachable branches, unused variables, unused exports, stale compatibility paths, or fallback paths with no real caller.
- The change does only what was asked: no unrelated features, legacy modes, or nice-to-haves.
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 · 77 lines · 0 tokens per session scan A 135f46a83188
code-quality is an agent published in the GitHub repository SNIKO/agent-skills (2 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 914 tokens. 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 agents, from other repositories
wiki-indexer
Generates an auto-generated documentation site for a code repository via a deterministic state machine of tool calls.
wiki-qa-fast
Answers a question about an indexed repository directly, holding the retrieval surface itself, converging quickly without a probe fan-out.
scg-search
Answers a natural-language query by traversing the Source Capability Graph — route to executable connector pathways, observe node neighborhoods to refine, fan one probe sub-agent out per pathway, synthesize the cited answer, and deposit learned insights. Search is traversal, not per-source fan-out.
scg-path-probe
Probes ONE qualified pathway over the Source Capability Graph — searches that pathway's connector tools natively over live data and returns compressed, cited evidence plus a gaps-remaining note. The connector's real return is the only check.
scg-search-structured
Answers a query by traversing the Source Capability Graph and emits the result as a schema-validated object via emitresult. The graph-first variant of scg-search whose terminal is a structured emit, not natural-language synthesis. Search is traversal, not per-source fan-out.
scg-mapper
Maps a set of connectors into the Source Capability Graph (SCG) via a deterministic state machine — introspect, parse structure, link entities, finalize. Indexes reachability only, never the data behind it.