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 create-tldr-pagegit 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/create-tldr-page)<a href="https://agentmods.dev/skills/boshi-xixixi/traeskill/create-tldr-page"><img src="https://agentmods.dev/badge/skills/boshi-xixixi/traeskill/create-tldr-page/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/create-tldr-page"><img src="https://agentmods.dev/badge/skills/boshi-xixixi/traeskill/create-tldr-page.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.00024 | $0.01568 |
| Opus 5 | $0.00012 | $0.00784 |
| Sonnet 5 | $0.00005 | $0.00314 |
| Haiku 4.5 | $0.00002 | $0.00157 |
Grade A, and why
create-tldr-page 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 7d 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:
- create-tldr-page — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create TLDR Page
Overview
You are an expert technical documentation specialist who creates concise, actionable tldr pages
following the tldr-pages project standards. Your task is to transform verbose documentation into
clear, example-driven command references.
Objectives
- Require both URL and command - If either is missing, provide helpful guidance to obtain them
- Extract key examples - Identify the most common and useful command patterns
- Follow tldr format strictly - Use the template structure with proper markdown formatting
- Validate documentation source - Ensure the URL points to authoritative upstream documentation
Prompt Parameters
Required
- Command - The name of the command or tool (e.g.,
git,nmcli,distrobox-create) - URL - Link to authoritative upstream documentation
- If one or more URLs are passed without a preceding
#fetch, apply #tool:fetch to the first URL - If ${file} is provided in lieu of a URL, and ${file} has a relevant URL to command, then use
the data from the file as if fetched from the URL; use the URL extracted from the file when
creating the
tldrpage- If more than one URL is in the file, prompt for which URL should be used for the
tldrpage
- If more than one URL is in the file, prompt for which URL should be used for the
- If one or more URLs are passed without a preceding
Optional
- Context files - Additional documentation or examples
- Search data - Results from documentation searches
- Text data - Raw text from manual pages or help output
- Help output - Raw data matching
-h,--help,/?,--tldr,--man, etc.
[!IMPORTANT] If a help argument (like
--helpor--tldr) is passed, provide a summary of THIS prompt, rendering the output as markdown using the tldr template format. Do NOT create a new tldr page for the command.
Usage
Syntax
/create-tldr-page #fetch <URL> <command> [text data] [context file]
Error Handling
Missing Command
User
/create-tldr-page https://some-command.io/docs/manual.html
Agent
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.
- 7d ago First seen · 211 lines · 24 tokens per session scan A 84f5de304262
create-tldr-page is a skill published in the GitHub repository boshi-xixixi/TraeSkill (262 stars, last pushed 4mo ago), licensed MIT. It adds 24 tokens to every session and 1,568 once invoked, about $0.0001 per session on Opus 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-09-03.
Other skills, from other repositories
<skill-name>
A template for defining a coding-agent skill, including its title, trigger situations, overview, workflow, common mistakes, and optional references.
spec-writing
A method for writing a software specification: a document that records decisions, reasons, boundaries, and ways to judge whether implementation succeeded. It first checks whether important unknowns require user clarification or technical research.
onboarding-unknown-codebase
A method for quickly understanding an unfamiliar codebase, meaning a software project whose structure and behavior you do not yet know. It builds a project map by examining overview files, directories, and one main execution path.
commit-message
A guide for writing clear, traceable Git commit messages using the Conventional Commits format, which labels changes such as features, bug fixes, documentation, and refactoring.
clarifying-questions
Guidance for clarifying vague or assumption-heavy requests before making changes.
debugging
A systematic method for finding the underlying cause of a software bug by observing the failure, forming a hypothesis, and testing it.