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/codekiln/logseq-cursor-rules/logseq-slidesgit clone --depth 1 https://github.com/codekiln/logseq-cursor-rulesWhat 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.00008 | $0.00502 |
| Opus 5 | $0.00004 | $0.00251 |
| Sonnet 5 | $0.00002 | $0.00100 |
| Haiku 4.5 | $0.00001 | $0.00050 |
Grade A, and why
logseq-slides 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 yesterday.
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
- Slides should follow this structure precisely:
- Each markdown unordered list item (
-) at the top level is treated as a section title (rendered as H2). - Nested markdown unordered list items (
\t-) represent individual slides. - Each slide should have multiple bullet points
*clearly describing the topic. - Include an image relevant to the slide content, following a 16:9 aspect ratio:
- For slides containing fewer than 10 words, images can be up to
680pxwide. - For slides containing more than 10 words, images should be approximately 400px wide.
- For slides containing fewer than 10 words, images can be up to
- Each markdown unordered list item (
- Prefer concise but clear bullet points on each slide.
- Example slide formatting:
- ## MCP Composability & [Sampling](https://modelcontextprotocol.io/docs/concepts/sampling)
* Every MCP client can be an MCP Server.
* [[MCP/Sampling]] allows **servers to request inference** from clients, ensuring **control of privacy and cost**.
{:height 225, :width 400}
- Use consistent image aspect ratios across slides, preferably 16:9.
- Keep each slide self-contained: one image, clear bullets, one coherent message.
- Don't break a single slide up into multiple slides by using hyphens rather than
*.
The following is three slides (three -)
<COUNTER_EXAMPLE>
- ## MCP Inspector & OAuth Authentication
- Inspector provides debugging for MCP connections.
- OAuth integration simplifies secure service authentication. Scoped permission boundaries can apply.
{:height 225, :width 400}
</COUNTER_EXAMPLE>
The following is a single slide (one -):
- ## MCP Inspector & OAuth Authentication
* Inspector provides debugging for MCP connections.
* OAuth integration simplifies secure service authentication. Scoped permission boundaries can apply.
{:height 225, :width 400}
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.
- yesterday First seen · 43 lines · 8 tokens per session scan A 970ef7995238
logseq-slides is a cursor rule published in the GitHub repository codekiln/logseq-cursor-rules (2 stars, last pushed 10mo ago), licensed MIT. It adds 8 tokens to every session and 502 once invoked, about $0.0000 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 cursor rules, from other repositories
new_features
Guidelines for integrating new features into the Task Master CLI.
utilities
// ✅ DO: Create focused, reusable utilities /.
dev_workflow
Guide for using Taskmaster to manage task-driven development workflows.
mcp
Guidelines for implementing and interacting with the Task Master MCP Server.
tests
Guidelines for implementing and maintaining tests for Task Master CLI.
commands
Guidelines for implementing CLI commands using Commander.js.