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 trae-op/electron-modular-boilerplate --skill rest-apigit clone --depth 1 https://github.com/trae-op/electron-modular-boilerplateWrote 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/trae-op/electron-modular-boilerplate/rest-api)<a href="https://agentmods.dev/skills/trae-op/electron-modular-boilerplate/rest-api"><img src="https://agentmods.dev/badge/skills/trae-op/electron-modular-boilerplate/rest-api/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/trae-op/electron-modular-boilerplate/rest-api"><img src="https://agentmods.dev/badge/skills/trae-op/electron-modular-boilerplate/rest-api.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.00040 | $0.00212 |
| Opus 5.5 | $0.00016 | $0.00085 |
| Sonnet 5.5 | $0.00008 | $0.00042 |
| Haiku 4.5 | $0.00004 | $0.00021 |
Grade A, and why
rest-api 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What ships with it
1 file 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.
- 1mo ago First seen · 28 lines · 40 tokens per session scan A 694a7c30dd94
rest-api is a skill published in the GitHub repository trae-op/electron-modular-boilerplate (5 stars, last pushed 8mo ago), with no licence file. It adds 40 tokens to every session and 212 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
backend-architect
Becomes a senior backend architect who designs scalable, resilient server-side systems with clear API contracts, sound data models, and documented trade-offs. Use when the user needs system design, database architecture, API contract definition, caching strategy, or backend technology selection. Do NOT use when…
api-designer
An API contract design guide for planning how software interfaces work before implementation. An API is an agreed way for programs or clients to exchange requests and responses.
api-reviewer
Use when the user asks to review or change an HTTP, RPC, event, CLI, or SDK API contract. Inspect routes, schemas, authorization, errors, compatibility, and consumers before editing, then verify request and response behavior with focused tests.
architecture-designer
Use when the user asks to design, compare, or revise a system architecture, component boundary, data flow, integration, or technical decision. Inspect the current topology and constraints first, make tradeoffs explicit, and define verification and migration paths before implementation.
contract-test-engineer
Use when the user asks to verify compatibility between an API provider and consumer, SDK and service, event producer and consumer, schema versions, or serialized data. Define and test the shared contract, including failures and compatibility rules, before changing either side.
mcp-server-building
Build a connector that lets AI agents use an outside service through well-designed tools (a Model Context Protocol server), in four phases: research, build, test, and prove it with realistic questions.