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-naming-conventionsgit 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.00014 | $0.00508 |
| Opus 5 | $0.00007 | $0.00254 |
| Sonnet 5 | $0.00003 | $0.00102 |
| Haiku 4.5 | $0.00001 | $0.00051 |
Grade A, and why
logseq-naming-conventions 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Logseq Naming Conventions
This is an extension to logseq-flavored-markdown logseq-flavored-markdown.mdc for maintaining consistent naming conventions in the knowledge graph.
Singular vs Plural Naming Convention
Core Principle
- Always use singular form in page names
- Use plural form in references through aliases
- This enables better extensibility through sub-namespaces
Implementation
-
Page Names
- Use singular form:
[[Related/Post]]not[[Related Topics]] - Use singular form:
[[Person]]not[[People]] - Use singular form:
[[Project]]not[[Projects]]
- Use singular form:
-
Aliases
- Add plural form as an alias in the page's frontmatter
- Example:
--- alias:: [[Related Posts]] ---
-
References
- Use plural form in references:
[[Related Posts]] - The alias will resolve to the singular page name
- This maintains consistency while allowing for sub-namespaces
- Use plural form in references:
Benefits
- Enables creation of sub-namespaces under singular forms
- Maintains clean URL structure
- Allows for both singular and plural references
- Supports hierarchical organization
Examples
<CORRECT_✅>
# Good Examples
- [[Person/John Smith]] (singular page name)
- alias:: [[People/John Smith]]
- [[Project/Cursor]] (singular page name)
- alias:: [[Projects/Cursor]]
- [[Related/Post]] (singular page name)
- alias:: [[Related Posts]]
<INCORRECT_❌>
# Bad Examples
- [[People/John Smith]] (plural in page name)
- [[Projects/Cursor]] (plural in page name)
- [[Related Topics]] (plural in page name)
</CORRECT_✅>
When to Use This Convention
- Creating new pages in the knowledge graph
- Adding aliases to existing pages
- Making references to pages
- Organizing hierarchical content
When Not to Use This Convention
- When the page represents a collection or category that is inherently plural
- When the page is a temporary or utility page
- When the page is a system page or configuration page
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 · 73 lines · 14 tokens per session scan A 166e6ba018e7
logseq-naming-conventions is a cursor rule published in the GitHub repository codekiln/logseq-cursor-rules (2 stars, last pushed 11mo ago), licensed MIT. It adds 14 tokens to every session and 508 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 cursor rules, from other repositories
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.
new_features
Guidelines for integrating new features into the Task Master CLI.
tests
Guidelines for implementing and maintaining tests for Task Master CLI.
commands
Guidelines for implementing CLI commands using Commander.js.