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/gosha70/code-copilot-team/wiki-first-querygit clone --depth 1 https://github.com/gosha70/code-copilot-teamWhat 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.00543 | $0.00543 |
| Opus 5 | $0.00271 | $0.00271 |
| Sonnet 5 | $0.00109 | $0.00109 |
| Haiku 4.5 | $0.00054 | $0.00054 |
Grade A, and why
wiki-first-query 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 2d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wiki-First Query Convention
This project maintains a curated knowledge layer at
knowledge/wiki/. It is the canonical home for durable project
knowledge — concepts, workflows, incidents, decisions, playbooks,
glossary entries, and known open questions. Every page is cited
back to a raw source.
The convention
When you start work on a topic that touches this project's domain (SDD workflow, peer review, adapter generation, agent safety, shape-up cycles, etc.), consult the wiki first:
- Read
knowledge/wiki/index.md(repo-relative path) to find pages relevant to your topic. - Follow the links into
concepts/,workflows/,incidents/,decisions/,playbooks/, orglossary/as relevant. - Treat what you find there as the project's current best understanding. Each page lists its sources in frontmatter; if you need deeper detail, follow those citations.
Only after consulting the wiki should you fall back to raw sources (specs, issues, PRs, code) for the same topic. The wiki exists so that you do not re-discover the same context every session.
When the wiki is silent or stale
If the wiki has nothing on the topic, or what it has is clearly out of date with the current code:
- Do the raw research yourself.
- If what you learn is reusable beyond this session, propose
a promotion by following the procedure in
knowledge/wiki/workflows/promote-lesson-to-wiki.md(repo-relative path). - Do not silently fix wiki content as a side effect of other work — wiki edits are intentional, single-purpose changes.
In Claude Code, the /promote-lesson <description> slash command
runs the promotion workflow on your behalf. Other adapters can
follow the workflow document directly.
What this convention does NOT do
- It does not require you to read every wiki page on every invocation. Read the index, then drill into what is relevant.
- It does not replace the SDD spec workflow. Specs still own feature requirements; the wiki holds knowledge that outlives any one feature.
- It does not replace session memory. Memory holds session ephemera; the wiki holds what survives.
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.
- 2d ago First seen · 60 lines · 543 tokens per session scan A 964517e0751c
wiki-first-query is a cursor rule published in the GitHub repository gosha70/code-copilot-team (6 stars, last pushed 2d ago), licensed MIT. It adds 543 tokens to every session, about $0.0027 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-31.
Other cursor rules, from other repositories
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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.