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/nextify-limited/libra/project-structuregit clone --depth 1 https://github.com/nextify-limited/libraWhat 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.04920 | $0.04920 |
| Opus 5 | $0.02460 | $0.02460 |
| Sonnet 5 | $0.00984 | $0.00984 |
| Haiku 4.5 | $0.00492 | $0.00492 |
Grade A, and why
project-structure 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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 · 539 lines · 4,920 tokens per session scan A 5d4baa6836b7
project-structure is a cursor rule published in the GitHub repository nextify-limited/libra (1,679 stars, last pushed 11mo ago), licensed AGPL-3.0. It adds 4,920 tokens to every session, about $0.0246 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-30.
Other cursor rules, from other repositories
ipc
You're building an Electron app following good security practices.
ai-development
When creating prompts for AI tools, follow this structure.
documentation
Use emoji icons consistently for better navigation.
cursorrules
As of July 2025, Cursor uses the .cursor/rules/ directory with modular .mdc files for all new projects. This .cursorrules file is supported for legacy compatibility only. Please migrate your rules to the new modular format for better organization, overrides, and AI context. See the Cursor Rules & Prompt Templates…
styling-guidelines
Cursor rule "styling-guidelines" from jalcantarab/v0-vibecodex, covering styling and design guidelines, tailwind css usage, 1. color palette, 2. typography and 3. spacing system.
react-components
Always use functional components with hooks. Follow this structure.