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 rnixai/rnix --skill code-analysisgit clone --depth 1 https://github.com/rnixai/rnixWrote 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/rnixai/rnix/code-analysis)<a href="https://agentmods.dev/skills/rnixai/rnix/code-analysis"><img src="https://agentmods.dev/badge/skills/rnixai/rnix/code-analysis/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/rnixai/rnix/code-analysis"><img src="https://agentmods.dev/badge/skills/rnixai/rnix/code-analysis.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.00032 | $0.00580 |
| Opus 5.5 | $0.00013 | $0.00232 |
| Sonnet 5.5 | $0.00006 | $0.00116 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
code-analysis 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 1mo 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Analysis
When to use this skill
Use this skill when the user asks to analyze, review, or audit source code for quality issues, bugs, or security vulnerabilities.
How to analyze code
- Use
Readto load the target file(s) - Examine code structure, naming conventions, error handling patterns
- Use
Grepto search for code patterns, andBashto run static analysis tools if available - If needed, use
Readto load related files (imports, tests, configs) for context
Tool usage guide
Read / Grep / Glob — Source inspection
Read— load target files to get full source code; load related import or config files for context; load test files to evaluate test coverageGrep— search for specific code patterns across files (prefer this over runninggrepthroughBash)Glob— enumerate related files by pattern (e.g.*.go); list a directory withpattern="*"
Bash — Shell command execution
Use for auxiliary analysis commands that have no dedicated tool:
wc -lto count file linesfind . -name "*.go" -type fto locate related files when a glob is insufficient
⚠️ Security constraint: Always append | head -N to limit Bash command output and avoid consuming context budget with large outputs.
Workflow
- Read target files — Use
Readto load user-specified files - Understand context — Analyze import dependencies, type definitions, interface contracts
- Analyze per dimension — Systematically check across all analysis dimensions
- Summarize findings — Organize all findings by severity level
- Output report — Output analysis results in structured format
Severity levels
- Critical — Must fix immediately. Includes: security vulnerabilities, data corruption risks, program crashes
- Warning — Should fix. Includes: potential bugs, performance issues, incomplete error handling
- Info — Suggested improvements. Includes: code style, readability, best practice deviations
Common patterns to check
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.
- 1mo ago First seen · 63 lines · 32 tokens per session scan A 49663eaba3ac
code-analysis is a skill published in the GitHub repository rnixai/rnix (5 stars, last pushed 2mo ago), licensed MIT. It adds 32 tokens to every session and 580 once invoked, about $0.0001 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
drug-design
End-to-end drug discovery pipeline orchestration. Deterministic Python script that auto-chains structure prediction, pocket detection, de novo design, docking, scoring, and ADMET filtering into reproducible workflows.
hypotheses
Turns a research direction into testable hypotheses with predictions, competing explanations and the experiments that discriminate between them, including the design (controls, randomization, blocking), sample size or seed count, the pre-specified analysis, and the result that would falsify each hypothesis. Use when a…
crit-cli
Use when an agent needs to author or reply to crit inline comments programmatically (including multi-agent workflows commenting on shared code/plans/docs/proposals), publish or unpublish a crit review with crit share, sync a crit review to or from a GitHub PR or GitLab MR, or read/interpret a crit review JSON file.…
crit
Review code changes, a plan, a live page (running dev server), or a local HTML file with Crit inline comments and structured human feedback. Use only when the user explicitly invokes /crit or directly asks to use Crit; a generic review request does not count.
crit-story
Author a crit story and continue the interactive review loop only when the user explicitly invokes crit-story or directly asks you to generate a crit story. Do not infer this skill from generic review, PR, or diff-review requests.
code-guidelines-go
Go 1.24–1.27 coding guidelines for the dimetron/pi-go AI agent runtime. Use this skill whenever writing, reviewing, or refactoring ANY Go code in pi-go. This covers idiomatic style, error handling, concurrency, project layout, testing (table-driven, fuzz, benchmarks, synctest), new stdlib usage, golangci-lint v2…