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 skills/avinava/anypoint-connect/code-reviewnpx skills add Avinava/anypoint-connect --skill code-reviewgit clone --depth 1 https://github.com/Avinava/anypoint-connectWhat 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.00044 | $0.00711 |
| Opus 5 | $0.00022 | $0.00356 |
| Sonnet 5 | $0.00009 | $0.00142 |
| Haiku 4.5 | $0.00004 | $0.00071 |
Grade A, and why
code-review 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 yesterday.
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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review anypoint-connect
Review against the repository's observable behavior and safety contracts. Use the user's requested scope; ask only when a missing decision would materially change the result.
Establish context
- Read the relevant implementation, tests, documentation, and current diff before drawing conclusions.
- Inspect
package.json,mkdocs.yml, and the applicable workflows when compatibility or release behavior is in scope. - Preserve unrelated working-tree changes. Use
rgorrg --filesfor discovery. - Report reviews evidence-first with file and line references. Implement changes only when requested.
Project invariants
Treat a violation of these contracts as a correctness or security issue:
- Authentication uses the user Authorization Code flow with
full offline_access; Client ID and Secret alone do not create an authorized session or provide supported headless CI authentication. - Authorization callbacks must be bound to a one-time state and an HTTP loopback host. Callback HTML must escape dynamic values and must not leak codes, state, secrets, or provider details to another origin.
- Client Secrets must not appear in command examples, logs, fixtures, screenshots, or realistic-looking literals. Interactive secret input stays masked. Profile configuration is user-restricted and tokens remain encrypted at rest.
- Credential precedence is process environment, active profile, then legacy project
.env. Changing credential sources does not replace browser authorization. - MCP mutations preview by default and require explicit confirmation. Production and deletion safeguards must remain bound to the reviewed target. Direct library clients do not inherit CLI/MCP confirmation gates.
- Operational CLI commands use the resolved active profile; only commands that actually declare
--profilemay be documented with it. - Examples use synthetic application, profile, organization, and environment names. Package pins in
README, docs, and examples match
package.json.
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.
- yesterday First seen · 72 lines · 44 tokens per session scan A ffa394d44d3f
code-review is a skill published in the GitHub repository Avinava/anypoint-connect (1 stars, last pushed 7d ago), licensed MIT. It adds 44 tokens to every session and 711 once invoked, about $0.0002 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.