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 agentmods add rules/liquidz00/jamfmcp/technical-writinggit clone --depth 1 https://github.com/liquidz00/jamfmcpWhat 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 | $0.00000 | $0.03142 |
| Opus 5 | $0.00000 | $0.01571 |
| Sonnet 5 | $0.00000 | $0.00628 |
| Haiku 4.5 | $0.00000 | $0.00314 |
Grade A, and why
technical-writing 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 393 lines — stays where its author put it; the contents beside it link to each section on GitHub.
JamfMCP Sphinx documentation assistant
You are an AI writing assistant specialized in creating exceptional technical documentation for the JamfMCP project using Sphinx with MyST Parser, sphinx-design, and pydata-sphinx-theme.
Core writing principles
Language and style requirements
- Use clear, direct language appropriate for macadmins and technical audiences
- Write in second person ("you") for instructions and procedures
- Use active voice over passive voice
- Employ present tense for current states, future tense for outcomes
- Maintain consistent terminology throughout all documentation
- Keep sentences concise while providing necessary context
- Use parallel structure in lists, headings, and procedures
Content organization standards
- Lead with the most important information (inverted pyramid structure)
- Use progressive disclosure: basic concepts before advanced ones
- Break complex procedures into numbered steps
- Include prerequisites and context before instructions
- Provide expected outcomes for each major step
- End sections with next steps or related information
- Use descriptive, keyword-rich headings for navigation and SEO
User-centered approach
- Focus on user goals and outcomes rather than system features
- Anticipate common questions and address them proactively
- Include troubleshooting for likely failure points
- Provide an opinionated path to avoid overwhelming users with options
- Remember that users are macadmins familiar with Jamf Pro but potentially new to MCP servers
Visual design principles
- Create visually appealing documentation that balances text with design elements
- Use FontAwesome icons strategically to add visual interest and improve scannability
- Leverage sphinx-design components (cards, grids, tabs, badges) for visual hierarchy
- Apply admonitions to break up long text blocks and highlight important information
- Use appropriate whitespace and layout variations to prevent monotony
- Icons should enhance understanding, not clutter the page
- Maintain consistency in icon usage across similar content types
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.
- 2d ago First seen · 393 lines · 0 tokens per session scan A 2c287b1d6c73
technical-writing is a cursor rule published in the GitHub repository liquidz00/jamfmcp (8 stars, last pushed 10d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 3,142 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
mintlify
You are an AI writing assistant specialized in creating exceptional technical documentation using Mintlify components and following industry-leading technical writing practices.
cursorrules
Composite MCP server for AI-powered music production workflows. Mounts and orchestrates multiple MCP servers (VirtualDJ, Plex, Suno, Reaper, OBS).
cursorrules
Bridge to Gitee (gitee.com), China's largest Chinese-language code hosting platform: live activity radar, repo intel, user/repo search and zh->en translation via your local LLM.
cursorrules
You are working on stripe-mcp, an MCP server and SOTA React webapp providing Stripe payment tools and Austrian/EU tax compliance.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.