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 TIKAZI/TIKAZ-AI-Skills --skill code-intelligencegit clone --depth 1 https://github.com/TIKAZI/TIKAZ-AI-SkillsWrote 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/tikazi/tikaz-ai-skills/code-intelligence)<a href="https://agentmods.dev/skills/tikazi/tikaz-ai-skills/code-intelligence"><img src="https://agentmods.dev/badge/skills/tikazi/tikaz-ai-skills/code-intelligence.svg" alt="Measured on agentmods" 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.00054 | $0.00460 |
| Opus 5 | $0.00027 | $0.00230 |
| Sonnet 5 | $0.00011 | $0.00092 |
| Haiku 4.5 | $0.00005 | $0.00046 |
Grade A, and why
code-intelligence 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 8d 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.
What it actually says
Code Intelligence
This public entry combines the local 代码-CodeGraph and 代码-GitNexus roles into one non-competing, clean-room workflow. This TIKAZ Edition is designed, integrated, refactored, and continuously maintained by TIKAZ.
Workflow
- Identify the repository, framework, entry points, tests, build commands, and local instructions.
- Build a compact map of modules, symbols, imports, data flow, and public boundaries.
- For a change, trace direct and indirect consumers before proposing edits.
- For a PR, review correctness, regressions, security, tests, and maintainability; cite files and lines.
- For a refactor, define invariants, migration steps, compatibility risks, and a rollback path.
- Validate with repository-native tests, type checks, lint, build, and focused impact checks.
Inputs and output contract
Accept a repository path or PR, the question or proposed change, and any known constraints. Return an evidence-backed architecture map, direct and indirect consumers, prioritized findings, an implementation or refactor plan, and verification results. Cite files and lines where possible; separate observed facts, inferences, and recommendations.
Validation and fallback
Cross-check the map against repository search, build metadata, tests, and call sites. If graph tooling is unavailable, fall back to repository-native search and explicit uncertainty rather than inventing relationships. Do not edit code unless the user also requests implementation.
Example
Use code-intelligence to map the authentication flow, find consumers of this API, and identify refactor risks before any edits.
Limits
Static analysis can miss runtime reflection, generated code, environment-specific wiring, and external consumers. Mark these gaps.
Source note
This role was written independently after studying the problem space. CodeGraph and GitNexus are research references only; no GitNexus code or documentation is distributed here.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 40 lines · 54 tokens per session scan A 9a548078b3d8
code-intelligence is a skill published in the GitHub repository TIKAZI/TIKAZ-AI-Skills (6 stars, last pushed 5d ago), licensed MIT. It adds 54 tokens to every session and 460 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
continual-learning
Nightly refinement of an existing per-repo review-style prompt using this reviewer's own finding outcomes. Read confirmed (resolved-by-commit / thumbs-up) and dismissed (thumbs-down) findings, promote the bug patterns the team actually fixes, demote the false-positive patterns, reconcile against the current prompt…
discount-review
Inspect the discount policy fixture with a repeatable review checklist and helper script.
code-review
Reviews code for bugs, security issues, and best practices.
chrome-cdp
Drive a headless Chrome over the Chrome DevTools Protocol (CDP) for browser QA — navigate, click, fill forms, read the DOM/accessibility tree, screenshot, and assert. Use whenever a task requires loading a web page and interacting with it like a user. Chrome is launched by a bash step (recipe below); this skill…
review-work
Quality gate: verify each acceptance criterion of a completed task/work unit, run quality checks, and create follow-up tasks for gaps. Use before merging or to audit delivered work. Invoked as /agiflow:review-work . Uses getworkunit, gettask, updatetask, createtask, createtaskcomment.
code-review-csharp
Perform structured code reviews of C# source code covering naming conventions, performance, security, readability, and .NET best practices. Trigger phrases include "review this C# code", "check my C# for best practices", "analyze this C# class", "find issues in my C# code".