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-forum-postgit 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.00000 | $0.01566 |
| Opus 5 | $0.00000 | $0.00783 |
| Sonnet 5 | $0.00000 | $0.00313 |
| Haiku 4.5 | $0.00000 | $0.00157 |
Grade A, and why
logseq-forum-post 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.
How it starts
The opening of the file, as written. The whole thing — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Formatting Forum Posts in Logseq
This rule defines the standard format for importing and structuring forum posts in Logseq, including posts from Cursor, Reddit, Stack Overflow, and other forums. This rule works in conjunction with [[logseq-person.mdc]] for handling person references.
⚠️ CRITICAL: DO NOT MODIFY FRONTMATTER TAGS ⚠️
- NEVER modify, add, or remove the
tags::frontmatter item specifically - The
tags::frontmatter (e.g.,tags:: [[MyTagHere]], [[MySecondTagHere]]) is strictly protected - Even if you think a tag is missing or incorrect, DO NOT change the
tags::frontmatter - This restriction applies ONLY to the
tags::frontmatter item, not to other page attributes
Basic Structure
- Forum posts should be structured hierarchically using Logseq's bullet-point system
- Each post should start with a title that links to the original post
- Use proper indentation with TAB characters
- All content must be prefixed with bullet points (
-)
Required Sections
-
Title and Link
- Format:
- # [Post Title - Forum Name](original-url) - Include the forum name in the title for clarity
- Example:
- # [How can I increase the indexing depth for @docs? - Discussion - Cursor - Community Forum](https://forum.cursor.com/t/how-can-i-increase-the-indexing-depth-for-docs/77949)
- Format:
-
Metadata
- Include creation date if available:
date-created:: [[YYYY/MM/DD]] - Include author if available:
- For known persons:
created-by:: [[Person/Full Name]] - For usernames:
created-by:: [[ForumName/User/Username]]
- For known persons:
- Add relevant tags:
tags:: [[ForumName]], [[Topic]]
- Include creation date if available:
-
Content Sections
- Original Poster:
- ## #[[Original Poster]]- For known persons:
[[Person/Full Name]] - For usernames:
[[ForumName/User/Username]]
- For known persons:
- Responses:
- ## #[[Response]]- Format each response with appropriate reference
- Related Topics:
- ## #[[Related/Post]] - My Notes:
- ## #[[My Notes]](for your personal annotations)
- Original Poster:
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 · 187 lines · 0 tokens per session scan A 40cb737238ac
logseq-forum-post is a cursor rule published in the GitHub repository codekiln/logseq-cursor-rules (2 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,566 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
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.