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 boshi-xixixi/TraeSkill --skill code-tourgit clone --depth 1 https://github.com/boshi-xixixi/TraeSkillWrote 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/boshi-xixixi/traeskill/code-tour)<a href="https://agentmods.dev/skills/boshi-xixixi/traeskill/code-tour"><img src="https://agentmods.dev/badge/skills/boshi-xixixi/traeskill/code-tour/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/boshi-xixixi/traeskill/code-tour"><img src="https://agentmods.dev/badge/skills/boshi-xixixi/traeskill/code-tour.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 4 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00184 | $0.05577 |
| Opus 5.5 | $0.00074 | $0.02231 |
| Sonnet 5.5 | $0.00037 | $0.01115 |
| Haiku 4.5 | $0.00018 | $0.00558 |
Grade A, and why
code-tour 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- code-tour — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 433 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Tour Skill
You are creating a CodeTour — a persona-targeted, step-by-step walkthrough of a codebase
that links directly to files and line numbers. CodeTour files live in .tours/ and work with
the VS Code CodeTour extension.
Two scripts are bundled in scripts/:
scripts/validate_tour.py— run after writing any tour. Checks JSON validity, file/directory existence, line numbers within bounds, pattern matches, nextTour cross-references, and narrative arc. Run it:python ~/.agents/skills/code-tour/scripts/validate_tour.py .tours/<name>.tour --repo-root .scripts/generate_from_docs.py— when the user asks to generate from README/docs, run this first to extract a skeleton, then fill it in. Run it:python ~/.agents/skills/code-tour/scripts/generate_from_docs.py --persona new-joiner --output .tours/skeleton.tour
Two reference files are bundled:
references/codetour-schema.json— the authoritative JSON schema. Read it to verify any field name or type. Every field you use must conform to it.references/examples.md— 8 real-world CodeTour tours from production repos with annotated techniques. Read it when you want to see how a specific feature (commands,selection,view,pattern,isPrimary, multi-tour series) is used in practice.
Real-world .tour files on GitHub
These are confirmed production .tour files. Fetch one when you need a working example of a specific step type, tour-level field, or narrative structure — don't write from memory when the real thing is one fetch away.
Find more with the GitHub code search: https://github.com/search?q=path%3A**%2F*.tour+&type=code
By step type / technique demonstrated
| What to study | File URL |
|---|---|
directory + file+line (contributor onboarding) |
https://github.com/coder/code-server/blob/main/.tours/contributing.tour |
selection + file+line + intro content step (accessibility project) |
https://github.com/a11yproject/a11yproject.com/blob/main/.tours/code-tour.tour |
Minimal tutorial — tight file+line narration for interactive learning |
https://github.com/lostintangent/rock-paper-scissors/blob/master/main.tour |
Multi-tour repo with nextTour chaining (cloud native OCI walkthroughs) |
https://github.com/lucasjellema/cloudnative-on-oci-2021/blob/main/.tours/introduction.tour |
isPrimary: true (marks the onboarding entry point) |
https://github.com/nickvdyck/webbundlr/blob/main/.tours/getting-started.tour |
pattern instead of line (regex-anchored steps) |
https://github.com/nickvdyck/webbundlr/blob/main/.tours/architecture.tour |
What ships with it
4 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.
- 1mo ago First seen · 433 lines · 184 tokens per session scan A 365f0d06c564
code-tour is a skill published in the GitHub repository boshi-xixixi/TraeSkill (278 stars, last pushed 5mo ago), licensed MIT. It adds 184 tokens to every session and 5,577 once invoked, about $0.0007 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-30.
Other skills, from other repositories
debugging
A systematic method for finding the underlying cause of a software bug by observing the failure, forming a hypothesis, and testing it.
error-handling
A guide to handling failures and recording useful logs in software. It explains when to pass an error upward, recover, reduce functionality, or retry temporary failures.
systematic-debugging
A step-by-step method for finding the underlying cause of technical problems before changing code. It covers reading errors, reproducing failures, checking recent changes, and tracing data across system components.
diagnosing-superpowers
A diagnostic workflow for investigating problems in Superpowers agent sessions using saved conversation records. It requires evidence linked to exact file paths and line numbers, then organizes findings into a report.
bug-investigator
Use when encountering any bug, test failure, or unexpected behavior during spec-superflow execution, before proposing fixes. Invoked automatically when build-executor hits a blockage.
azure-network-watcher
Expert knowledge for Azure Network Watcher development including troubleshooting, decision making, limits & quotas, security, configuration, and integrations & coding patterns. Use when configuring VNet/NSG flow logs, Traffic Analytics, packet capture, Connection Monitor migration, or VPN monitoring, and other Azure…