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 skills add gosha70/code-copilot-team --skill wiki-first-querygit clone --depth 1 https://github.com/gosha70/code-copilot-teamWrote 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/skills/gosha70/code-copilot-team/wiki-first-query)<a href="https://agentmods.dev/skills/gosha70/code-copilot-team/wiki-first-query"><img src="https://agentmods.dev/badge/skills/gosha70/code-copilot-team/wiki-first-query/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/skills/gosha70/code-copilot-team/wiki-first-query"><img src="https://agentmods.dev/badge/skills/gosha70/code-copilot-team/wiki-first-query.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.00037 | $0.00543 |
| Opus 5.5 | $0.00015 | $0.00217 |
| Sonnet 5.5 | $0.00007 | $0.00109 |
| Haiku 4.5 | $0.00004 | $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 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 — 59 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.
- 1mo ago First seen · 59 lines · 37 tokens per session scan A 03354410fbbc
wiki-first-query is a skill published in the GitHub repository gosha70/code-copilot-team (7 stars, last pushed 17d ago), licensed MIT. It adds 37 tokens to every session and 543 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other skills, from other repositories
agent-deck-recall
Record and later find what an agent-deck session was for, across harnesses, and hand a past conversation to the current one. Use when the user says "remember what this session was for", "tag this session", "annotate", "mark the outcome", "ticket for this session", "find the session where we...", "what did we decide…
rosetta
Reconcile ALL prior agent conversations (Claude Code, Codex, Droid/Factory, Hermes, Cursor) with git history and docs into a cited ground truth, and distill durable decision records (ADRs/PDRs/BDRs). Use whenever the user wants to catch up on or get the state of a project, build or refresh a ground truth, read or mine…
pact-recall
Search PACT's vector memory for relevant bugs, solutions, research, and feedback.
agent-v3-memory-specialist
Agent skill for v3-memory-specialist - invoke with $agent-v3-memory-specialist.
agent-deck
Helper scripts live in this skill's scripts/ folder. Resolve them from the base directory shown when the skill loaded, not from the user's project.
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…