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 aiya000/dotfiles --skill define-markdown-formatgit clone --depth 1 https://github.com/aiya000/dotfilesWrote 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/aiya000/dotfiles/define-markdown-format)<a href="https://agentmods.dev/skills/aiya000/dotfiles/define-markdown-format"><img src="https://agentmods.dev/badge/skills/aiya000/dotfiles/define-markdown-format/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/aiya000/dotfiles/define-markdown-format"><img src="https://agentmods.dev/badge/skills/aiya000/dotfiles/define-markdown-format.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00023 | $0.00287 |
| Opus 5.5 | $0.00009 | $0.00115 |
| Sonnet 5.5 | $0.00005 | $0.00057 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
define-markdown-format 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
define-markdown-format
以降の Markdown 編集・作成時に、以下のルールを適用するのです。
Section Spacing
Add a blank line between the title and the first list item if adding new sections with list items.
Also do not add trailing dot to list items like - An item.
Always add blank lines before and after section headers (lines starting with ## or ###).
For example:
## Section Title
- First item
- Second item
### Subsection Title
- Another item
List Indentation
- Use 4 spaces for nested list items
- Never use 2 spaces for indentation in markdown lists
Example:
- First level item
- Second level item (4 spaces)
- Third level item (8 spaces)
Trailing Spaces for Line Breaks
IMPORTANT: In Markdown (CommonMark), two trailing spaces at the end of a line ( ) represent a hard line break (<br>).
- DO NOT remove trailing spaces (two spaces) at the end of lines
- These are intentional and used for formatting
- Removing them will break the intended line breaks in rendered Markdown
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 · 50 lines · 23 tokens per session scan A 0ad0ab2972eb
define-markdown-format is a skill published in the GitHub repository aiya000/dotfiles (21 stars, last pushed 3d ago), licensed MIT. It adds 23 tokens to every session and 287 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.
Other skills, from other repositories
restart__pull_request
A pull-request restart workflow for replacing a messy review with a new pull request containing one clean commit and a summary of the earlier discussion.
rescue__pull_request_review
An automated workflow for handling GitHub pull-request review comments, applying requested code changes, committing them, and pushing them back.
submit__pull_request
An automated pull-request submission workflow. A pull request is a request for a code change to be reviewed and merged; this workflow writes its explanation, creates it, watches its automated checks, and fixes failed checks.
write__pull_request
A workflow for writing a pull request description, the explanation attached to a proposed code change for review. It analyses the changes and commit history.
monitor__ci_status
An automated monitor for GitHub Actions, the service that runs checks such as tests after code changes. It watches all checks after a pull request or a push to a pull-request branch and can invoke a failure-recovery process.
monitor__pull_request_conflict
An automated check for GitHub pull requests, which are proposed code changes awaiting review or merging.