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 desirecore/market --skill code-intelligencegit clone --depth 1 https://github.com/desirecore/marketWrote 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/desirecore/market/code-intelligence)<a href="https://agentmods.dev/skills/desirecore/market/code-intelligence"><img src="https://agentmods.dev/badge/skills/desirecore/market/code-intelligence/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/desirecore/market/code-intelligence"><img src="https://agentmods.dev/badge/skills/desirecore/market/code-intelligence.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.00196 | $0.01777 |
| Opus 5.5 | $0.00078 | $0.00711 |
| Sonnet 5.5 | $0.00039 | $0.00355 |
| Haiku 4.5 | $0.00020 | $0.00178 |
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 25d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
code-intelligence Skill
L0: One-line Summary
Use DesireCore's hidden Lsp tool for semantic code navigation through an already-installed Language Server.
L1: When to Use
Activate this skill when the task depends on symbol meaning rather than text matching:
- Jump to a symbol's definition or implementation.
- Find all semantic references to a symbol.
- Inspect type information or documentation at a source position.
- List the symbols in one file or search symbols across the workspace.
- Find callers and callees through the LSP call hierarchy.
Hard rules
- Semantic-navigation requests (definitions, references, implementations, call relations, symbols) MUST try
Lspfirst; never answer them fromGrep/Globtext matching without tryingLsp. - Falling back to text search is allowed only when: the
Lspcall errors, the target language is not in the supported mappings, or the Language Server is missing and the user has not asked to install it. - Every answer that falls back to text search MUST explicitly tell the user that the result comes from text matching, not semantic analysis, and why (for example "typescript-language-server is not installed"). In large repositories, or with same-named symbols, overloads, or inheritance, text matching can be wrong — never let the user mistake it for semantic navigation.
- Purely textual searches (string literals, log copy) are out of scope for this skill; use
Grep/Globdirectly.
L2: Operating Procedure
1. Check the workspace boundary
Lsp starts an external indexing process that can read the authorized workspace. The target file therefore needs directory-level read access. If the tool reports that an exact-file grant is insufficient, ask the user to authorize the project directory through ManageWorkDirs; never widen the scope silently.
2. Choose one operation
| Operation | Purpose | Required input |
|---|---|---|
goToDefinition |
Find where a symbol is defined | file, line, character |
findReferences |
Find semantic references, including the declaration | file, line, character |
hover |
Read type information or documentation | file, line, character |
documentSymbol |
Outline symbols in one file | file |
workspaceSymbol |
Search named symbols in the current workspace | file, non-empty query |
goToImplementation |
Find concrete implementations | file, line, character |
prepareCallHierarchy |
Resolve a callable item at a position | file, line, character |
incomingCalls |
Find functions or methods that call the target | file, line, character |
outgoingCalls |
Find functions or methods called by the target | file, line, character |
What ships with it
2 files 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.
- 25d ago Changed · +1 lines cacc218ff0d7
- 1mo ago First seen · 141 lines · 196 tokens per session scan A 5be9c681fb34
code-intelligence is a skill published in the GitHub repository desirecore/market (2 stars, last pushed yesterday), licensed MIT. It adds 196 tokens to every session and 1,777 once invoked, about $0.0008 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
codebase-navigator
Rapidly understand any codebase: identify entry points, map architecture, find key patterns, summarize modules, trace data flow.
repo-map
A map of a code repository built from its syntax tree, showing symbols, structure, and dependencies. An AST is the structured representation a programming language uses to understand source code.
sparc-methodology
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration.
swarm-advanced
Advanced swarm orchestration patterns for research, development, testing, and complex distributed workflows.
agent-harness-fault-injection
Use when an agent workflow needs deterministic recovery evidence for sandbox, MCP/tool, worker, checkpoint, memory, or orchestration failures.
agent-reels
Find animation and video references on 1human, consult a human-agent shared library, and contribute public creations only with prior owner permission.