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/sync-workflow)<a href="https://agentmods.dev/rules/secondlifes/code-intel/sync-workflow"><img src="https://agentmods.dev/badge/rules/secondlifes/code-intel/sync-workflow/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/sync-workflow"><img src="https://agentmods.dev/badge/rules/secondlifes/code-intel/sync-workflow.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.01542 | $0.01542 |
| Opus 5.5 | $0.00617 | $0.00617 |
| Sonnet 5.5 | $0.00308 | $0.00308 |
| Haiku 4.5 | $0.00154 | $0.00154 |
Grade A, and why
sync-workflow 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
94% identical to sync-workflow — 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Config Source of Truth & Sync Workflow
This repo supports five AI coding tools (Claude Code, Cursor, Codex CLI, GitHub
Copilot, Gemini/Antigravity CLI). To avoid maintaining near-duplicate copies by
hand, most content has a single canonical source under .agents/.
Where content actually lives
| Content | Canonical source | Generated / native copies |
|---|---|---|
| Rules (per-topic, glob-scoped) | .agents/rules/*.md |
.claude/rules/*.md and .cursor/rules/*.mdc — generated, do not hand-edit. Note the extension: Cursor recognizes only .mdc under .cursor/rules and silently ignores .md there (cursor.com/docs/rules). |
| Slash commands | .agents/commands/*.md |
.claude/commands/*.md — generated, do not hand-edit |
| Skills | .agents/skills/*/SKILL.md |
content is never copied, but Claude Code needs an entry point: a generated junction/symlink per skill at .claude/skills/<skill-name> → .agents/skills/<skill-name>. Claude Code additionally gets a generated thin wrapper at .claude/commands/<skill-name>.md so the skill is also invocable as an explicit /<skill-name> command — see below. |
| Root universal summary | AGENTS.md |
none — hand-authored, references .agents/rules for detail |
| Gemini/Antigravity summary | .gemini/rules/project-rules.md |
none — hand-authored, same role as AGENTS.md but Gemini-specific |
| Copilot pre-prompt | .github/copilot-instructions.md |
none — hand-authored, references AGENTS.md |
| Kiro steering docs | .kiro/steering/*.md |
none — different concept (living project context, not per-topic rules), intentionally out of this sync scheme |
Mandatory workflow
Whenever you add, edit or delete a file under .agents/rules/ or
.agents/commands/, OR add/remove a skill folder under .agents/skills/,
immediately run the generator before finishing your turn:
pwsh tools/generate-ai-configs.ps1
This copies the current source into .claude/rules (as .md) and
.cursor/rules (as .mdc), copies commands into .claude/commands,
generates one .claude/commands/<skill-name>.md wrapper per folder under
.agents/skills/, links each of those skill folders into .claude/skills/,
and removes any generated file, wrapper or link whose source was deleted. If a skill's folder name collides with a
hand-authored file under .agents/commands/, the script skips generating a
wrapper for it and prints a warning — hand-authored commands always win.
Never hand-edit files inside .claude/rules/, .cursor/rules/ or
.claude/commands/ directly — they will be silently overwritten on the next
run and any change made only there will be lost.
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 Changed · +12 lines · +173 tokens per session f3c9db055f3b
- 1mo ago First seen · 90 lines · 1,369 tokens per session scan A d80c682a2536
sync-workflow is a cursor rule published in the GitHub repository SecondLifes/code-intel (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 1,542 tokens to every session, about $0.0062 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to sync-workflow, 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).