Borrowing it
Nothing to install: this file belongs to opencue/cuecards. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/opencue/cuecards/main/.agents/skills/trace-mcp/SKILL.mdgit clone --depth 1 https://github.com/opencue/cuecardsWrote 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/opencue/cuecards/trace-mcp)<a href="https://agentmods.dev/skills/opencue/cuecards/trace-mcp"><img src="https://agentmods.dev/badge/skills/opencue/cuecards/trace-mcp.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.00052 | $0.01267 |
| Opus 5 | $0.00026 | $0.00633 |
| Sonnet 5 | $0.00010 | $0.00253 |
| Haiku 4.5 | $0.00005 | $0.00127 |
Grade A, and why
trace-mcp 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 3d 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.
This is a copy
97% identical to trace-mcp — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
trace-mcp — Code Intelligence Routing
trace-mcp is a framework-aware code intelligence MCP server. It exposes 120+ tools that return semantic, structured results over a cross-language dependency graph. When trace-mcp is available, it is almost always cheaper and more accurate than native file tools.
When to Use
Activate this skill whenever you need to:
- Find a function, class, method, route, component, or any symbol
- Understand a file, module, or feature before editing
- Determine what breaks if you change something
- Trace a request flow, call graph, or data flow
- Audit architecture, dead code, tests, or security
Do not use Read, Grep, Glob, or shell ls/find/cat/head/tail for exploring source code (.ts, .js, .py, .php, .go, .rb, .java, etc.). Use trace-mcp tools instead. Native tools stay allowed only for non-code files (.md, .json, .yaml, configs) or immediately before an Edit on a known file.
Start-of-Session Checklist
get_project_mapwithsummary_only=true— orient yourself to the project structureget_task_contextwithtask: "<natural-language description>"— gather all relevant code in a single call instead of chainingsearch→get_symbol→Read
Decision Matrix
| Task | trace-mcp tool | Instead of |
|---|---|---|
| Find a symbol by name | search |
Grep |
| Understand a file before editing | get_outline |
Read (full file) |
| Read one symbol's source | get_symbol |
Read (full file) |
| Multiple symbols + shared imports | get_context_bundle |
chained get_symbol |
| What breaks if I change X | get_change_impact |
guessing |
| Who calls this / what does it call | get_call_graph |
Grep |
| All usages of a symbol | find_usages |
Grep |
| Implementations of an interface | get_type_hierarchy |
Grep / ls |
| Classes implementing X | search with implements filter |
Grep |
| Tests for a symbol or file | get_tests_for |
Glob + Grep |
| Project overview | get_project_map (summary_only) |
Bash ls/find |
| Context for a task | get_task_context / get_feature_context |
reading many files |
| HTTP request flow | get_request_flow |
reading route + controller files |
| DB model relationships | get_model_context |
reading model + migrations |
| Component tree | get_component_tree |
reading component files |
| Circular dependencies | get_circular_imports |
manual tracing |
| Dead code / dead exports | get_dead_code / get_dead_exports |
Grep for unused |
| Project health / coverage gaps | self_audit |
manual inspection |
| Complexity / hotspots | get_complexity_report / get_risk_hotspots |
guessing |
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.
- 3d ago First seen · 89 lines · 52 tokens per session scan A 6748b4400263
trace-mcp is a skill published in the GitHub repository opencue/cuecards (5 stars, last pushed today), licensed MIT. It adds 52 tokens to every session and 1,267 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to trace-mcp, differing in 8 lines, and is treated as a copy.
Other skills, from other repositories
atomic-debug
Hypothesis-driven debugging skill. Use when a bug, test failure, crash, or unexpected behavior is reported. Auto-trigger on error pastes or "broken/doesn't work/failing" language. Explicit invocation: /atomic-debug. Output: symptom statement → hypothesis table → cheapest test first → root cause. No symptom-patching.…
system-health
Suggest whether the machine needs a DISK or MEMORY cleanup — and catch the case where Heimdall ITSELF is the hog (runaway orphaned python from the presence keeper). Use when the machine is slow / swapping / laggy, disk or "System Data" is full, memory is exhausted, at the start of a long session, or when the user asks…
debug
Structured debugging workflow for investigating issues.
fix-issue
Analyze and fix a GitHub issue with structured workflow.
stuck
Diagnose frozen, stuck, or slow Qwen Code sessions on this machine. Scans for problematic processes, high CPU/memory usage, hung subprocesses, and debug logs. Use /stuck or /stuck to focus on a specific process.
structured-debugging
Hypothesis-driven debugging methodology for hard bugs. Use this skill whenever you're investigating non-trivial bugs, unexpected behavior, flaky tests, or tracing issues through complex systems. Activate proactively when debugging requires more than a quick glance — especially when the first attempt at a fix didn't…