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/clivechung/skillmcp/tremnpx skills add clivechung/skillmcp --skill tremgit clone --depth 1 https://github.com/clivechung/skillmcpWrote 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/clivechung/skillmcp/trem)<a href="https://agentmods.dev/skills/clivechung/skillmcp/trem"><img src="https://agentmods.dev/badge/skills/clivechung/skillmcp/trem.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 | $0.00051 | $0.01433 |
| Opus 5 | $0.00026 | $0.00717 |
| Sonnet 5 | $0.00010 | $0.00287 |
| Haiku 4.5 | $0.00005 | $0.00143 |
Grade A, and why
trem 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 4d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TREM Code Review & Verification
A software engineering quality framework founded on four pillars:
- T - Testable: Decoupled, deterministic, dependency-injected, and easily unit-testable.
- R - Readable: Self-documenting, low cognitive complexity, with comments explaining non-obvious why rather than what.
- E - Extensible: Open for extension, closed for modification, leveraging design patterns and composition.
- M - Maintainable: Single responsibility, small blast radius, structured error handling, and high refactorability.
⚡ Quick Assessment Checklist
When evaluating or generating any block of code, verify these core questions:
| Pillar | Focus Area | Verification Question |
|---|---|---|
| T (Testable) | Decoupling & DI | Can every unit be tested in complete isolation without real I/O, network, or global state? |
| R (Readable) | Clarity & Intent | Can a new engineer understand the business logic in 60 seconds without decrypting magic logic? |
| E (Extensible) | Open/Closed | Can new features/strategies be added without modifying existing tested core functions? |
| M (Maintainable) | Cohesion & Blast Radius | Does every module have a single reason to change with predictable, graceful error handling? |
🛠️ Workflows
Workflow 1: Code Review & PR Audit
Use this workflow to review existing code or proposed pull requests.
- Analyze Code Structure: Read the source files and identify module boundaries, dependencies, and control flows.
- Evaluate Against TREM Pillars:
- Testability Audit: Look for hardcoded dependencies (
new Service()), hidden globals, static clocks, and coupled I/O. - Readability Audit: Check for deep nesting (>3 levels), ambiguous names, missing rationale comments, and complex boolean logic.
- Extensibility Audit: Check for large
switch/if-elsechains on types, lack of interfaces/adapters, and tight vendor coupling. - Maintainability Audit: Check for god functions (>40 lines), shotgun surgery risks, swallowed errors, and missing boundary validation.
- Testability Audit: Look for hardcoded dependencies (
- Generate Structured TREM Report: Produce the review using the standard template below.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 125 lines · 51 tokens per session scan A f8c72b9a0f2f
trem is a skill published in the GitHub repository clivechung/skillmcp (0 stars, last pushed 4d ago), licensed MIT. It adds 51 tokens to every session and 1,433 once invoked, about $0.0003 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…