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 opus-4-7-featuresgit 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/opus-4-7-features)<a href="https://agentmods.dev/skills/gosha70/code-copilot-team/opus-4-7-features"><img src="https://agentmods.dev/badge/skills/gosha70/code-copilot-team/opus-4-7-features/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/opus-4-7-features"><img src="https://agentmods.dev/badge/skills/gosha70/code-copilot-team/opus-4-7-features.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.02265 |
| Opus 5.5 | $0.00015 | $0.00906 |
| Sonnet 5.5 | $0.00007 | $0.00453 |
| Haiku 4.5 | $0.00004 | $0.00227 |
Grade A, and why
opus-4-7-features 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 27d 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Opus 4.7 Features & Optimization
Optional guidance for sessions using Claude Opus 4.7 (v2.1.111+). Load this rule when you want to leverage Opus 4.7-specific capabilities.
Adaptive Thinking (Breaking Change)
Opus 4.7 changes the API contract for extended thinking. The legacy form is rejected:
thinking: {type: "enabled", budget_tokens: N}→ returns 400 Bad Request on Opus 4.7.- Only
thinking: {type: "adaptive"}is accepted.
With adaptive thinking, the model dynamically decides when and how much to think based on query complexity. There is no fixed token budget — Claude self-regulates depth.
How to control depth:
- Use the
effortparameter (xhigh/high/medium/low) instead ofbudget_tokens. - Thinking is also promptable in-message:
- "Think carefully and step-by-step" → encourages deeper reasoning.
- "Prioritize responding quickly" → encourages a shorter thinking pass.
Older models: enabled/budget_tokens is deprecated on Opus 4.6 and Sonnet 4.6 (still functional today, but on the way out). Migrate to adaptive proactively so your code keeps working when the deprecation lands.
Effort Level: xhigh
Opus 4.7 introduces a new effort level xhigh between high and max. Other models fall back to high when xhigh is requested.
| Effort | When to use | Phase fit |
|---|---|---|
low |
Quick lookups, file searches, trivial edits | — |
medium |
Standard implementation, build tasks | Build |
high |
Architecture, planning, detailed review | Research, Plan, Review |
xhigh |
Complex multi-file reasoning, deep architectural analysis, hard debugging | Plan (large features), Review (cross-cutting PRs) |
Availability: xhigh became selectable in Claude Code v2.1.111+ when running Opus 4.7.
Default change: From Claude Code v2.1.117+, xhigh is the default effort level for Opus 4.7. On v2.1.111–v2.1.116 the default is still high and you must opt in with /effort xhigh. Other models continue to default to high regardless of Claude Code version.
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.
- 27d ago Changed · +36 lines 42a402bdae99
- 1mo ago First seen · 141 lines · 37 tokens per session scan A 64150a169029
opus-4-7-features 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 2,265 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
fleet
Fan out a fleet of independent agent-deck child sessions from inside a session and check their progress non-blockingly. Use when the user wants to "launch several/N sessions", "fan out", "run agents in parallel", "spin up a fleet", "kick off background agents", or "check progress from the main session" without…
watcher-creator
Guide for creating agent-deck watchers conversationally. This skill should be used when users want to set up a new watcher (webhook, ntfy, github, slack, gmail) to route events to a conductor. It walks the user through selecting an adapter type, gathering required settings, generating watcher.toml and clients.json…
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…
x-spec
A system-planning guide that turns a vague idea into a set of linked design documents. It defines goals, modules, interfaces, data, workflows, and ways to check the result.
x-audit-arch
A project-wide architecture review skill that checks whether code is placed in the right modules and whether important definitions have one reliable source.