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.
git clone --depth 1 https://github.com/jeffgreendesign/textrawlWrote 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/rules/jeffgreendesign/textrawl/documentation)<a href="https://agentmods.dev/rules/jeffgreendesign/textrawl/documentation"><img src="https://agentmods.dev/badge/rules/jeffgreendesign/textrawl/documentation/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/rules/jeffgreendesign/textrawl/documentation"><img src="https://agentmods.dev/badge/rules/jeffgreendesign/textrawl/documentation.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.00000 | $0.00474 |
| Opus 5.5 | $0.00000 | $0.00190 |
| Sonnet 5.5 | $0.00000 | $0.00095 |
| Haiku 4.5 | $0.00000 | $0.00047 |
Grade A, and why
documentation 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
Documentation Standards
File Structure
docs/
├── README.md # Main overview (in docs/, not root)
├── CLI.md # CLI tool documentation
├── SECURITY.md # Security and RLS guide
├── DESKTOP.md # Desktop app documentation
└── DOCS-PLAYGROUND-FRAMEWORK.md # Framework spec
Root-level files:
CLAUDE.md- AI coding assistant instructionsAGENTS.md- Agent conventions and tool guideCONTRIBUTING.md- Contribution guidelinesllms.txt- AI sitemap
Markdown Conventions
Headings
Use ATX-style headings with blank lines:
# Title
## Section
### Subsection
Code Blocks
Always specify language for syntax highlighting:
```typescript
const example = 'code';
### Tables
Use consistent alignment:
```markdown
| Column 1 | Column 2 |
|----------|----------|
| Value 1 | Value 2 |
Links
Use reference-style for repeated links:
See the [CLI documentation][cli] for details.
[cli]: docs/CLI.md
RFC 2119 Language
Use precise language for requirements in tool documentation:
- MUST / REQUIRED: Absolute requirement
- SHOULD / RECOMMENDED: Strong recommendation
- MAY / OPTIONAL: Truly optional
Example:
The
queryparameter MUST be provided. Thetagsparameter MAY be omitted.
Tool Documentation Template
### tool_name
Brief description of what the tool does.
**Parameters:**
- `param` (type, REQUIRED): Description
- `optionalParam` (type, OPTIONAL): Description, default: value
**Response:**
```json
{ "example": "response" }
Errors:
| Error | Cause | Fix |
|---|---|---|
| Error name | Why it happens | How to fix |
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 · 104 lines · 0 tokens per session scan A b1d05a66bd21
documentation is a cursor rule published in the GitHub repository jeffgreendesign/textrawl (5 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 474 tokens. 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 cursor rules, from other repositories
cursor-rules
Generated by mdvs scaffold snippet --platform cursor. -->.
mdvs
../../../crates/mdvs/scaffolding/snippet/cursor-rules.mdc.
svelte
You are an expert in Svelte 5, SvelteKit, TypeScript, and modern web development.
frontend
Demo Shop frontend guidance.
write
Writing style guide with AI detection avoidance. For tweets, LinkedIn, blogs, READMEs, commits. Activate with @write.
npm-cli-packaging-agent
Apply when preparing a TypeScript CLI tool for distribution via npm, specifically when configuring package.json, handling executables, and considering cross-platform compatibility. Covers the bin field, shebang line (#!/usr/bin/env node), pre-publish checks, installation instructions, and Node engine compatibility.