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/SecondLifes/code-intelWrote 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/secondlifes/code-intel/kit-settings)<a href="https://agentmods.dev/rules/secondlifes/code-intel/kit-settings"><img src="https://agentmods.dev/badge/rules/secondlifes/code-intel/kit-settings/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/secondlifes/code-intel/kit-settings"><img src="https://agentmods.dev/badge/rules/secondlifes/code-intel/kit-settings.svg" alt="Reviewed on agentmods" width="80" 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.00697 | $0.00697 |
| Opus 5.5 | $0.00279 | $0.00279 |
| Sonnet 5.5 | $0.00139 | $0.00139 |
| Haiku 4.5 | $0.00070 | $0.00070 |
Grade A, and why
kit-settings 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 1mo 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.
This is a copy
100% identical to kit-settings — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kit Settings (settings.json) — Rules
Every kit ships a settings.json at its own root (next to AGENTS.md,
README.md) — committed to git, unlike analysis/ (gitignored,
local-only). Think of it like a package.json's version field: it is
this repo's own source of truth for its own operational state, not a
shared cross-kit file like the workspace root's template-vars.json
(which holds identity/legal values substituted once at kit-creation
time and never touched again).
Current schema
{
"$comment": "Per-kit operational settings — committed to git. Extend with new top-level keys as needs arise; document each addition here and in this file's own $comment.",
"versioning": {
"scheme": "semver",
"current_version": "0.1.0"
}
}
versioning.current_version— this kit's current released version. This is the value the fix-publication workflow reads before tagging and writes back after bumping — see.agents/skills/rad-prompt-studio/references/prompts/edit-base-prompt.md's Golden Rule 7. The annotated git tag (vMAJOR.MINOR.PATCH) must always match this value; if they ever disagree,settings.jsonis correct and the tag needs to catch up (or vice versa if a tag was created without updating this file — audit which one is stale from the actual git tag list and the CHANGELOG, don't guess).versioning.scheme— currently always"semver". Present so a future non-semver kit isn't forced into the wrong assumption silently.
Extensibility
This file is deliberately small today and expected to grow — new top-level keys get added here as real needs arise (the workspace owner described this explicitly: "ileride çok genişletilebilir"). When adding a new key:
- Document it in this rule file (schema + meaning) before or alongside introducing it in code/workflow.
- Keep it kit-local operational state — identity/legal/contributor data
still belongs in the workspace root's
template-vars.json, not here. - Never store secrets (API keys, tokens, credentials) in this file — it is committed and public once the kit is published.
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.
- 1mo ago First seen · 61 lines · 697 tokens per session scan A f8f0826c21aa
kit-settings is a cursor rule published in the GitHub repository SecondLifes/code-intel (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 697 tokens to every session, about $0.0028 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to kit-settings, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).