agentmods.dev

tour

tour is a skill for Claude Code from drafthq/draft. It costs 31 tokens per session (647 once invoked), scanned A, original, MIT.

An interactive guide for a new engineer learning an existing codebase. It introduces the system one part at a time and asks questions during the walkthrough.

In plain words
What is it for?
Use it to get an onboarding tour, understand the entry point and modules, and learn how the project's technology and data-persistence rules work.
Why use it?
It avoids overwhelming newcomers with the entire architecture and checks their understanding before revealing more detail.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the draft plugin — 33 skills shipped together

not rated 40repo today A scan SkillSpector: pass 31 tokens original MIT

Good fit Use it to get an onboarding tour, understand the entry point and modules, and learn how the project's technology and data-persistence rules work.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/drafthq/draft/tour
View source ↗ drafthq/draft getdraft.dev
Install

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.

Any agent
npx skills add drafthq/draft --skill tour
Clone the repo
git clone --depth 1 https://github.com/drafthq/draft

Made for: Claude Code.

Or install draft, the plugin that ships this one along with the rest of its 33 skills.

Wrote 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.

agentmods badge for tour

README.md
[![agentmods](https://agentmods.dev/badge/skills/drafthq/draft/tour/github.svg)](https://agentmods.dev/skills/drafthq/draft/tour)
Your own site
<a href="https://agentmods.dev/skills/drafthq/draft/tour"><img src="https://agentmods.dev/badge/skills/drafthq/draft/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.

agentmods 80×15 button for tour

Your own site · 80×15
<a href="https://agentmods.dev/skills/drafthq/draft/tour"><img src="https://agentmods.dev/badge/skills/drafthq/draft/tour.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 647 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00031 $0.00647
Opus 5.5 $0.00012 $0.00259
Sonnet 5.5 $0.00006 $0.00129
Haiku 4.5 $0.00003 $0.00065

Measured 1mo ago against content hash d9fd9532ba6e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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.

skills/tour/SKILL.md · 40 lines

How it starts

The opening of the file, as written. The whole thing — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Draft Tour: Interactive Onboarding

Provide an interactive codebase walk-through based on existing architecture and guardrail constraints.

Red Flags - STOP if you're

  • Dumping the entire architecture.md into the chat window.
  • Giving answers to foundational pattern questions before prompting the developer to guess.
  • Explaining code the developer hasn't explicitly asked to view yet.

Execution Constraints

  1. Load Context: Read draft/architecture.md, draft/tech-stack.md, and draft/guardrails.md.
  2. Interactive Cadence: Ask the developer if they are familiar with the tech stack constraints found in draft/tech-stack.md.
  3. Module Introduction: Instead of listing all modules, introduce the "Entry Point" module first.
  4. Active Challenge: After explaining a module's responsibility, challenge the developer: "Based on our Context-Driven Development rules, how do you think we handle data persistence here?" Wait for their answer before revealing the architecture strategy.
    • If the answer is correct, confirm briefly and cite the supporting line in architecture.md / guardrails.md.
    • If the answer is partially right, name what they got right, then ask a narrower follow-up (e.g., "Right that we cache reads — what's the invalidation trigger?") before revealing the rest.
    • If the answer is wrong, do not just hand them the answer. Quote the specific guardrail or HLD section that contradicts it, then re-prompt with a hint scoped to that section.
  5. Traceability: Highlight draft/.state/facts.json showing how module constraints have evolved.
  6. Track Lifecycle Walk: Show the full feature lifecycle and who owns each gate:
    • /draft:new-track → spec.md (requirements + classification + approvers) + plan.md (phases/tasks)
    • /draft:decompose → hld.md (always, with graph-derived diagrams) + lld.md (when --lld or High-complexity module)
    • Approvers (HLD): Technical Leads, Architecture Review Board, Cloud Operations (SaaS), QA Leads (on-prem), PM Leads
    • Approvers (LLD): Team Leads, Technical Leads, Quality Assurance
    • /draft:implement → TDD loop reading lld.md/hld.md for stub generation
    • /draft:upload → blocks git upload for high/mission-critical tracks until HLD §Approvals signed
    • /draft:deploy-checklist → blocks deploy until HLD §Checklist + LLD §Alerting Thresholds populated
    • Walk a real example track from draft/tracks/ if any exist; otherwise sketch a hypothetical low-criticality flow.
  7. Completion: Guide the developer to create their first test track using /draft:new-track so they understand the artifact loop end-to-end.

Read the full file on GitHub · 40 lines

Changes

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.

  1. 1mo ago First seen · 40 lines · 31 tokens per session scan A d9fd9532ba6e

Subscribe to this mod's changes

tour is a skill published in the GitHub repository drafthq/draft (40 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 647 once invoked, about $0.0001 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.

Claude CodeCode reviewLearning and teachingai-code-reviewai-codingcopilotcursor
Related

Other skills, from other repositories

gentle-ai-collab-perfect

Trigger: contributing to Gentleman-Programming/gentle-ai as an external collaborator. Strict issue-first workflow, honest PR bodies, contributor-vs-maintainer scope, chained-PR strategy, verification protocol, docstring coverage. Load whenever the active repo is Gentleman-Programming/gentle-ai and any part of the…

Gentleman-Programming/gentle-ai · 106 tokens

issue-creation

Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.

Gentleman-Programming/gentle-ai · 30 tokens

branch-pr

Create Gentle AI pull requests with issue-first checks. Trigger: creating, opening, or preparing PRs for review.

Gentleman-Programming/gentle-ai · 26 tokens

skill-creator

Trigger: new skills, agent instructions, documenting AI usage patterns. Create LLM-first skills with valid frontmatter.

Gentleman-Programming/gentle-ai · 27 tokens

work-unit-commits

Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.

Gentleman-Programming/gentle-ai · 33 tokens

cognitive-doc-design

Design docs that reduce cognitive load. Trigger: writing guides, READMEs, RFCs, onboarding, architecture, or review-facing docs.

Gentleman-Programming/gentle-ai · 33 tokens