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 chen3feng/agent-skills --skill url-space-after-bracketsgit clone --depth 1 https://github.com/chen3feng/agent-skillsWrote 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/chen3feng/agent-skills/url-space-after-brackets)<a href="https://agentmods.dev/skills/chen3feng/agent-skills/url-space-after-brackets"><img src="https://agentmods.dev/badge/skills/chen3feng/agent-skills/url-space-after-brackets/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/chen3feng/agent-skills/url-space-after-brackets"><img src="https://agentmods.dev/badge/skills/chen3feng/agent-skills/url-space-after-brackets.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.00465 |
| Opus 5 | $0.00012 | $0.00233 |
| Sonnet 5 | $0.00005 | $0.00093 |
| Haiku 4.5 | $0.00002 | $0.00047 |
Grade A, and why
url-space-after-brackets 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 9d 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
URL space after brackets
When to use
You're writing or editing Markdown content that contains URLs, especially when the text after the URL contains Chinese characters, asterisks, or other special characters that could be misinterpreted as part of the URL.
Problem
When generating URLs in Markdown without a trailing space, browsers and parsers may incorrectly include subsequent characters as part of the URL, leading to 404 errors:
[中文文档](https://example.com/doc)**重要**
In this example, **重要** becomes part of the URL: https://example.com/doc**重要** which results in a 404 error.
Solution
Always add a space after the closing bracket of a URL in Markdown:
[中文文档](https://example.com/doc) **重要**
The space acts as a clear delimiter, ensuring the URL ends where intended.
Example
Wrong way (causes 404):
查看[快速入门指南](https://example.com/guide)了解更多细节。
Resulting URL: https://example.com/guide了解更多细节。
Right way (works correctly):
查看[快速入门指南](https://example.com/guide) 了解更多细节。
Resulting URL: https://example.com/guide
Pitfalls
- This applies to all URL formats in Markdown:
[text](url),, and reference-style links - The issue is particularly common with Chinese text where spaces are less visually obvious
- Some Markdown parsers are more lenient than others, but for maximum compatibility always include the space
- Don't confuse this with the space inside the brackets - that's for readability and doesn't affect URL parsing
See also
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.
- 9d ago First seen · 58 lines · 24 tokens per session scan A 3fc61031c937
url-space-after-brackets is a skill published in the GitHub repository chen3feng/agent-skills (5 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 24 tokens to every session and 465 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-08-31.
Other skills, from other repositories
format-converter-brief
Produces a clear, step-by-step brief explaining exactly how to convert a finished article or document from one format (Word, plain text, InDesign export) into a specified target format (Markdown, HTML, or structured plain text), preserving all editorial elements correctly.
mr-li-writer
A Chinese-language editing and writing workflow for turning ideas, source material, or rough topics into publishable content. It adapts the structure and wording to formats such as WeChat articles, Zhihu answers, Xiaohongshu posts, websites, and blogs.
format-markdown
Formats Markdown files consistently using project-native tooling first (repo scripts/config), then safe fallback formatters, and verifies the result with lint/check commands. Invoked when the user asks to format markdown, tidy docs, normalize README files, or fix markdown style drift.
note-organizer
Use this skill whenever the user wants to organize course materials, lecture notes, PPT/PDF/DOCX files, textbooks, personal notes, senior-student notes, historical exams, review questions, standards, manuals, or scattered study resources into a structured Markdown note library. Use it even when the user only says…
github-format-standards
Use when the user wants to share a project to GitHub. Runs a full pipeline: root audit, file naming and structure, document fixes (headings, code-block language tags, table alignment, explicit command interpreters), generate missing files (LICENSE, .gitignore, CONTRIBUTING.md, Issue/PR templates), README rewrite…
github-format-standards
A workflow for preparing a project for publication on GitHub, a website for hosting and sharing code. It reviews the project, fixes documentation and structure, creates common project files, and can create and push a repository.