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/SYZ-Coder/codebase-knowledge-wikiWrote 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/syz-coder/codebase-knowledge-wiki/cross-tech-stack-spec-skill)<a href="https://agentmods.dev/rules/syz-coder/codebase-knowledge-wiki/cross-tech-stack-spec-skill"><img src="https://agentmods.dev/badge/rules/syz-coder/codebase-knowledge-wiki/cross-tech-stack-spec-skill/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/syz-coder/codebase-knowledge-wiki/cross-tech-stack-spec-skill"><img src="https://agentmods.dev/badge/rules/syz-coder/codebase-knowledge-wiki/cross-tech-stack-spec-skill.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.00000 | $0.01343 |
| Opus 5.5 | $0.00000 | $0.00537 |
| Sonnet 5.5 | $0.00000 | $0.00269 |
| Haiku 4.5 | $0.00000 | $0.00134 |
Grade A, and why
cross-tech-stack-spec-skill 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.
How it starts
The opening of the file, as written. The whole thing — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cross Tech Stack Spec Skill
Use this rule as an extension to backend-service-spec-skill.mdc when one of these is true:
- the user explicitly asks for cross-tech-stack analysis or mixed-stack mapping
- the target repository is primarily mobile, H5, web frontend, Python, data, worker, script, or mixed-stack
- the requested route crosses page, app, client, backend, task, callback, webhook, bridge, gateway, or message boundaries
Do not use this rule by default for ordinary backend-only microservice analysis. In that case, use backend-service-spec-skill.mdc.
Required Skill Source
Before producing artifacts, read the skill source from one of these locations:
- If this skill library exists in the target project:
cross-tech-stack-spec-skill/SKILL.md - If copied under a shared skill folder:
skills/cross-tech-stack-spec-skill/SKILL.md - If cloned as a project-local rule source:
ai-skill-lib/cross-tech-stack-spec-skill/SKILL.md - Also read
backend-service-spec-skill/SKILL.md,skills/backend-service-spec-skill/SKILL.md, orai-skill-lib/backend-service-spec-skill/SKILL.mdbecause this rule extends the backend service workflow instead of replacing it.
Read only the relevant reference files when they exist:
cross-tech-stack-spec-skill/references/mobile-project-guidelines.mdcross-tech-stack-spec-skill/references/h5-project-guidelines.mdcross-tech-stack-spec-skill/references/python-project-guidelines.mdcross-tech-stack-spec-skill/references/mixed-stack-routing-guidelines.mdcross-tech-stack-spec-skill/references/workspace-layering-template.mdcross-tech-stack-spec-skill/references/mixed-stack-noise-exclusion-guide.mdcross-tech-stack-spec-skill/references/interface-mapping-template.mdcross-tech-stack-spec-skill/references/communication-matrix-guidelines.mdcross-tech-stack-spec-skill/references/communication-evidence-levels.mdcross-tech-stack-spec-skill/references/mixed-stack-domain-mapping-guidelines.mdcross-tech-stack-spec-skill/references/incremental-update-mode.mdcross-tech-stack-spec-skill/references/activation-and-boundaries.mdcross-tech-stack-spec-skill/references/diagram-output-guidelines.mdcross-tech-stack-spec-skill/references/mermaid-safety-checklist.zh-CN.md
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 · 144 lines · 0 tokens per session scan A 007baced6820
cross-tech-stack-spec-skill is a cursor rule published in the GitHub repository SYZ-Coder/codebase-knowledge-wiki (9 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,343 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
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).