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 ericrisco/rsc-harness --skill makegit clone --depth 1 https://github.com/ericrisco/rsc-harnessWrote 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/ericrisco/rsc-harness/make)<a href="https://agentmods.dev/skills/ericrisco/rsc-harness/make"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/make/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/ericrisco/rsc-harness/make"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/make.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 72 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- high Tool Misuse · line 166 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- medium Data Exfiltration · line 113 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00127 | $0.03260 |
| Opus 5.5 | $0.00051 | $0.01304 |
| Sonnet 5.5 | $0.00025 | $0.00652 |
| Haiku 4.5 | $0.00013 | $0.00326 |
Grade A, and why
make scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -H "Authorization: Token $MAKE_API_TOKEN" \ How it starts
The opening of the file, as written. The whole thing — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Make (Integromat) — operate scenarios by REST API and MCP
Drive a live Make.com account from code or an agent: create scenarios from a
blueprint, activate/run/stop/clone/delete them, and manage the connections,
hooks, data stores, and teams around them. This skill owns the operate
half — the API v2 calls and the MCP wiring. It does not design the flow;
what a scenario should do (trigger, routes, mapping, dedup, error handler)
lives in automation-flows, and the
Make-vs-n8n-vs-Zapier billing call lives in
automation-strategy. Bring the design
here, and this skill turns it into API payloads and MCP tool calls.
Reality up top (verify at author time — Make ships fast):
- REST API v2 is GA. Base URL is zoned:
https://{zone}.make.com/api/v2. - The Make MCP server is GA and free on every plan — you only pay the scenario credits a run consumes. Cloud MCP has two tool tiers: run tools (all plans) and management tools (paid).
Connect first — API token vs MCP
Two ways in, chosen by who is driving:
- REST API v2 — deterministic CRUD from your own scripts/CI. Full control of the blueprint. Use for provisioning, bulk edits, activate/stop pipelines.
- Make MCP server — lets an MCP client (Claude, Cursor, ChatGPT) call your scenarios and (on paid plans) manage them as tools, no glue code. Use when an agent is the operator.
.env (never inline secrets — read from the environment):
MAKE_ZONE=eu2.make.com # your org's zone — eu1|eu2|us1|us2 (+ celonis). WRONG ZONE = AUTH ERROR.
MAKE_API_TOKEN=xxxxxxxx # Profile → API/SDK → API token. Scopes are FIXED at creation.
MAKE_TEAM_ID=123456 # teamId a scenario is created under (integer)
MAKE_MCP_TOKEN=yyyyyyyy # separate MCP token, for the token-URL MCP transport
Auth header (API): Authorization: Token {MAKE_API_TOKEN} — the literal
word Token, a space, then the token. OAuth2 is the alternative for
multi-user apps. Scopes are chosen when the token is minted and cannot be
widened later — mint with scenarios:read scenarios:write (and
connections, hooks, datastores, teams as needed) up front; a
too-narrow token means re-minting, not patching.
What ships with it
5 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.
- 1mo ago First seen · 256 lines · 127 tokens per session scan A 9bfb59833c0a
make is a skill published in the GitHub repository ericrisco/rsc-harness (314 stars, last pushed yesterday), licensed MIT. It adds 127 tokens to every session and 3,260 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
api-design-conventions
Use when you design or change an endpoint's errors, status codes, pagination, idempotency or concurrency behaviour — one error shape, the status-code table, bounded lists, safe retries.
api-security-checklist
Use when you add or change an endpoint, an auth check, a query by id, an outbound call to a user-supplied URL, file handling, or anything touching credentials — the OWASP API Top 10 (2023) as concrete Go and Java checks.
fiber-rest-api
Use when adding or changing a Go HTTP endpoint — Fiber v2 or v3 (detect which), thin handlers, central error mapping, boundary validation; the same rules apply to net/http, chi, echo or gin.
api-contract-openapi
Use when you add or change any HTTP endpoint's request or response shape (Go or Java) — implement the task's contract exactly, evolve additively, keep the OpenAPI document in sync, and detect breaking changes before hand-off.
spine-design
Produce a system design doc — components, data flow, decisions made, tradeoffs, failure modes. Not a list of options. An actual design with calls made. Use when asked for "system design for", "architect this", "how should we build", or "design the backend".
spine-api
Design and spec an API — endpoints, request/response shapes, error codes, auth pattern, pagination. Applies Stripe's consistency principles. Use when asked to "design an API", "build API endpoints", "create REST API", or "API for this feature".