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 skills/rnixai/rnix/code-analysisnpx skills add rnixai/rnix --skill code-analysisgit clone --depth 1 https://github.com/rnixai/rnixWhat 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.00032 | $0.00580 |
| Opus 5 | $0.00016 | $0.00290 |
| Sonnet 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 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 — 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.
- yesterday 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 23d ago), licensed MIT. It adds 32 tokens to every session and 580 once invoked, about $0.0002 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
foundry-hosted-agent-validation
Step-by-step process for validating a Python Foundry hosted agent sample (under python/samples/04-hosting/foundry-hosted-agents/) end to end — running it locally (native runtime and azd ai agent run) and after deploying it to an Azure AI Foundry project with azd. Use this when asked to validate a hosted agent sample.
python-feature-lifecycle
Guidance for package and feature lifecycle in the Agent Framework Python codebase, including stage meanings, feature-stage decorators, feature enums, and how to move APIs from one stage to the next.
python-development
Coding standards, conventions, and patterns for developing Python code in the Agent Framework repository. Use this when writing or modifying Python source files in the python/ directory.
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
trigger-authoring-tasks
Covers writing backend Trigger.dev tasks with @trigger.dev/sdk: defining task() and schemaTask(), the run function and its ctx, retries, waits, queues and concurrency, idempotency keys, run metadata, logging, triggering other tasks (and the Result shape), scheduled/cron tasks, and the essentials of trigger.config.ts.…
background
Use when the user wants to see, inspect, cancel, or prune background agents fired during prior chain runs. Read/manage .hyperflow/background/registry.json and the per-agent output buffers at .hyperflow/background/ .md. Standalone — never auto-invoked. Trigger with /hyperflow:background, "list background agents"…