Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/gosha70/code-copilot-teamnpx agentmods add commands/gosha70/code-copilot-team/add-entryWrote 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/commands/gosha70/code-copilot-team/add-entry)<a href="https://agentmods.dev/commands/gosha70/code-copilot-team/add-entry"><img src="https://agentmods.dev/badge/commands/gosha70/code-copilot-team/add-entry.svg" alt="Measured on agentmods" 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.00303 |
| Opus 5 | $0.00000 | $0.00151 |
| Sonnet 5 | $0.00000 | $0.00061 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
add-entry 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 3d 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.
What it actually says
/add-entry
Add a new entry to the pack content.
Procedure
- Open
content/data.tbx(or the active content file declared incontent/manifest.yaml). - Append a new
<termEntry id="t-NNNN">block. Pick a freshid— never reuse an existing one. Consumers may pin to it. - Fill in
<term>,<termNote type="partOfSpeech">,<descrip type="definition">. If you have a verifiable source, add a<descrip type="source">line. - If this is the first content change since the last release, bump the minor version in
content/manifest.yaml(additive change). If you are removing or renaming an entry, bump the major version instead. - Run schema validation locally:
xmllint --noout content/data.tbx - Sync into both wrappers and run their test suites:
bash scripts/sync-content.sh (cd jvm-wrapper && ./gradlew test) (cd python-wrapper && pytest) - Commit with a message that includes the entry id and the version bump.
Refuse to merge if
- An existing entry's
idwas reused. - The manifest version was not bumped.
- Either wrapper's test suite fails.
- The schema validator fails.
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.
- 3d ago First seen · 28 lines · 0 tokens per session scan A fed21df8694f
add-entry is a command published in the GitHub repository gosha70/code-copilot-team (6 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 303 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-09-03.
Other commands, from other repositories
report
Generer des rapports QA Recette a partir des donnees de session.
brief-compliance-check
Check a LaTeX coursework submission against the requirements in a supplied PDF assessment brief. Use when verifying format, required sections, word limits, or deliverables before submission. Not for general prose proofreading; use $proofread.
plugin-commands
:::info This document covers all build, test, and smoke commands for eIsland native plugins. Each plugin lives under plugins/ and has its own package.json with independent scripts. ::.
speckit.clarify
This project uses the GAIA preset. Bare /speckit-clarify is not the clarify path here: core clarify writes an off-shape artifact (a ## Clarifications / ### Session block with five-word answers) and carries a question cap GAIA does not use. Run /gaia-spec instead — it drives GAIA's coverage-based Socratic clarify loop…
test-commands
:::info This document covers the testing commands for running, filtering, and measuring test coverage in the eIsland frontend. ::.
import
Import an existing markdown E2E ledger (directives, credentials, phases, tests, runs) into the database.