Borrowing it
Nothing to install: this file belongs to timohaa/scopewalker-mcp. 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/timohaa/scopewalker-mcp/main/.agents/skills/create-tool/SKILL.mdgit clone --depth 1 https://github.com/timohaa/scopewalker-mcpWrote 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/timohaa/scopewalker-mcp/create-tool)<a href="https://agentmods.dev/skills/timohaa/scopewalker-mcp/create-tool"><img src="https://agentmods.dev/badge/skills/timohaa/scopewalker-mcp/create-tool/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/timohaa/scopewalker-mcp/create-tool"><img src="https://agentmods.dev/badge/skills/timohaa/scopewalker-mcp/create-tool.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.00019 | $0.00106 |
| Opus 5.5 | $0.00008 | $0.00042 |
| Sonnet 5.5 | $0.00004 | $0.00021 |
| Haiku 4.5 | $0.00002 | $0.00011 |
Grade A, and why
create-tool 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.
What it actually says
Create Tool
Read the repository Codex workflow adapters, then read and follow the shared create-tool workflow. Apply the adapters to Claude-specific instructions. Resolve workflow paths from the repository root, including when invoked from a subdirectory. Preserve arguments supplied with the invocation.
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 Changed · -1 tokens per session d8d2f9ea35d9
- 1mo ago Changed · -10 tokens per session 49d84dc1d9e9
- 1mo ago Changed · -33 lines 6c05b75bf0d0
- 1mo ago First seen · 46 lines · 30 tokens per session scan A a5740167dea5
create-tool is a skill published in the GitHub repository timohaa/scopewalker-mcp (1 stars, last pushed 6d ago), licensed MIT. It adds 19 tokens to every session and 106 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-31.
Other skills, from other repositories
setup-config
Analyze a repository and generate an intelligent omen.toml with project-specific defaults. Use when starting Omen in a new project.
track-trends
Analyze repository health trends over time using historical git commits. Use for quarterly reports, release retrospectives, or tracking technical debt paydown progress.
assess-impact
Analyze blast radius before changing specific files. Use before refactoring core components, making breaking API changes, or modifying shared code to identify affected files and stakeholders.
audit-architecture
Audit module coupling, cohesion, hidden dependencies, and design smells. Use when conducting architecture reviews, evaluating design decisions, or identifying structural tech debt.
onboard-codebase
Generate onboarding guide with key symbols, architecture overview, and subject matter experts. Use when joining a new project, onboarding teammates, or creating project documentation.
report-debt
Generate comprehensive tech debt assessment with quantified metrics and prioritized issues. Use for sprint planning, stakeholder reports, or justifying refactoring time allocation.