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.
git clone --depth 1 https://github.com/Garyzhu-hub/software-controlled-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/garyzhu-hub/software-controlled-skills/project-indexing)<a href="https://agentmods.dev/rules/garyzhu-hub/software-controlled-skills/project-indexing"><img src="https://agentmods.dev/badge/rules/garyzhu-hub/software-controlled-skills/project-indexing.svg" alt="Measured on agentmods" height="20"></a>What 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.1 | $0.00000 | $0.03244 |
| Opus 5 | $0.00000 | $0.01622 |
| Sonnet 5 | $0.00000 | $0.00649 |
| Haiku 4.5 | $0.00000 | $0.00324 |
Grade A, and why
project-indexing 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 8d ago.
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 — 620 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: project-indexing description: Graph-aware multi-platform project indexing skill. Use this skill to initialize, rebuild, refresh, or audit AI-readable project indexes for web, backend, full-stack, iOS, Android, mini program, macOS, desktop, Electron, Tauri, Flutter, React Native, CI, test, and documentation projects.
Project Indexing Skill v2.2.0 — Graph-aware Project Indexing
1. Role
You are a graph-aware multi-platform repository indexing agent.
Your job is to analyze the current repository and create or update AI-readable project index files under:
docs/ai-index/
This skill is for indexing only. Do not implement product features, fix bugs, refactor code, add dependencies, change configuration, install tools, initialize optional code graph systems, or modify production behavior unless the user explicitly asks for that in a separate task.
2. Core Objective
Build compact, accurate, platform-aware indexes that help future coding agents understand:
- What kind of project this is.
- Which platforms are present.
- Where key source files live.
- Which commands validate the project.
- Which files are safe to modify for common tasks.
- Which files or areas are high-risk.
- Which specialized indexes should be read for future tasks.
- Which entry points, key symbols, dependency boundaries, critical flows, and affected tests are known or uncertain.
- Whether optional structured code intelligence is available, fresh, useful, incomplete, stale, or absent.
3. Supported Project Types
Detect one or more of the following project types:
web-frontend
server-backend
fullstack
api
database
auth-security
ios
android
miniprogram
macos
desktop
electron
tauri
flutter
react-native
cross-platform-mobile
cli
library-package
test
ci-build
docs
A repository may contain multiple project types.
4. Required Index Files
Always create or update:
docs/ai-index/PROJECT_INDEX.md
docs/ai-index/INDEX_CHANGELOG.md
Create platform-specific indexes only when relevant:
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.
- 8d ago First seen · 620 lines · 0 tokens per session scan A 7c93bb24118a
project-indexing is a cursor rule published in the GitHub repository Garyzhu-hub/software-controlled-skills (4 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,244 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
mempalace-recall-always
Always-on MemPalace recall — search the palace before answering about past work, people, projects, or prior decisions.
dreamd-recall
Recall lessons, decisions, and prior context from the .agent/ memory daemon. Use when starting work in a project that has a .agent/ folder, when the user references a past decision, or when you are about to make a choice that has a documented prior.
session-memory
Use at conversation wrap-up or when the user explicitly indicates end-of-session — capture residual lessons not captured in-flight.
common_memory_bank
I am Cursor, an expert software engineer with a unique characteristic: my memory resets completely between sessions. This isn't a limitation - it's what drives me to maintain perfect documentation. After each reset, I rely ENTIRELY on my Memory Bank to understand the project and continue work effectively. I MUST read…
context-recorder-system
A modular system for recording project context, decisions, requirements, and lessons in structured files. It divides the recorder into core, template, advanced, and edge-case modules.
self-improving-obsidian-llm-wiki
LLM Wiki OS operating rules.