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-persongit 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.00011 | $0.00640 |
| Opus 5 | $0.00005 | $0.00320 |
| Sonnet 5 | $0.00002 | $0.00128 |
| Haiku 4.5 | $0.00001 | $0.00064 |
Grade A, and why
logseq-person 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
How a Person is tracked in this Logseq knowledge garden
This is an extension to logseq-flavored-markdown logseq-flavored-markdown.mdc for recording information about a person.
A person entry is a logseq page where the page title matches one of the following patterns:
- [[People/Full Name]] (corresponds to
pages/People___Full Name.md) - [[Person/Full Name]] (corresponds to
pages/Person___Full Name.md) - [[/People/Full Name]] (e.g.,
pages/HU___People___Full Name.md) - [[/Person/Full Name]] (e.g.,
pages/AI___Person___Full Name.md)
When to Create a Person Page
Person pages should only be created for individuals who meet one or more of these criteria:
- Known across multiple platforms (e.g., GitHub, Twitter, Stack Overflow)
- Have a confirmed real identity
- Are significant contributors or maintainers
- Have a substantial online presence
- Are key figures in their field
For other users, use site-specific namespaces:
[[CursorAI/Forum/User/Username]]for Cursor Forum users[[Reddit/User/Username]]for Reddit users[[StackOverflow/User/Username]]for Stack Overflow users[[ForumName/User/Username]]for other forum users
Creating a Person Page
If you are asked to make an entry for a person, you should:
-
Search First
- Search in
pages/People___*.md,pages/Person___*.md, and in any file matchingpages/**___People___*.mdorpages/**___Person___*.mdto find if a person already exists - If it already exists, then you should update the existing entry
- A single person should not have more than one person page
- Search in
-
Verify Significance
- Confirm the person meets the criteria for a person page
- If not, use the appropriate site-specific namespace instead
-
Create/Update Page
- If a new person page is needed, create it under
[[Person/Full Name]]by default - If the person is referenced in other contexts/namespaces (e.g.,
[[People/Full Name]],[[HU/Person/Full Name]]), add aliases in the frontmatter to those contexts usingalias::(notaliases::) - Look up the person on the internet
- Create a person page for them if they meet the criteria
- Link the person and a bit of their bio in their page
- If possible add an image link
- Include relevant external links (GitHub, LinkedIn, etc.)
- If a new person page is needed, create it under
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 · 52 lines · 11 tokens per session scan A aca74eaf839e
logseq-person is a cursor rule published in the GitHub repository codekiln/logseq-cursor-rules (2 stars, last pushed 10mo ago), licensed MIT. It adds 11 tokens to every session and 640 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
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.