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 connect-toolgit 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/connect-tool)<a href="https://agentmods.dev/skills/ericrisco/rsc-harness/connect-tool"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/connect-tool/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/connect-tool"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/connect-tool.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.00098 | $0.02484 |
| Opus 5.5 | $0.00039 | $0.00994 |
| Sonnet 5.5 | $0.00020 | $0.00497 |
| Haiku 4.5 | $0.00010 | $0.00248 |
Grade B, and why
connect-tool scanned grade B 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 6d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- **Secrets stay in `.env`** (gitignored, `chmod 600`). Never in the repo, never in `02-DOCS`. How it starts
The opening of the file, as written. The whole thing — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Connect a tool: research it, pick the safe route, prove it works
The user said "connect my Holded", "can the agent read our Sage?", "hook up WhatsApp". This
skill turns that sentence into a working, documented connection in 01-TOOLS/<TOOL>/, for any
tool: the ones with a modern API, and the program installed on an office PC fifteen years ago.
rsc ships no ready-made connections. Every project builds only the ones its user asks for, so the method matters more than any list of vendors: find the truth, take the least dangerous route, prove it, leave it written down.
Before anything: what does the user want to do?
Ask only what the docs cannot answer, in plain words (technical_level in
02-DOCS/wiki/harness/user-profile.md sets the register):
- Which product, exactly? Name, edition, version. "Sage" is five different products.
- Where does it run? In the cloud (a website they log into) or installed on a computer or server in the office.
- Read or write? Reports and questions need reading. Entering invoices needs writing, and writing is a separate, explicit decision (below).
1. Research: the docs decide, never memory
Look it up every time, even for a tool you "know": plans, endpoints and MCP servers change monthly. In this order, stopping when the route is clear:
- The vendor's own developer docs: search
<product> API,<product> developers,<product> MCP. Prefer the vendor domain over blog posts. - The official MCP registry (
registry.modelcontextprotocol.io) and the vendor's docs for an official MCP server. An official, read-only MCP is often the fastest safe route. - Library docs through Context7 when the route is an SDK.
- Export and import features in the product's user manual: scheduled CSV/Excel exports, FTP drops, official import file formats.
- Where the data lives for installed software: the vendor's installation guide, the database engine it installs (often SQL Server Express, sometimes Access, Firebird or MySQL).
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.
- 6d ago Changed · -10 lines 7f995e0c75c7
- 7d ago First seen · 174 lines · 98 tokens per session scan B a5c8069fa182
connect-tool is a skill published in the GitHub repository ericrisco/rsc-harness (225 stars, last pushed 2d ago), licensed MIT. It adds 98 tokens to every session and 2,484 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-10.
Other skills, from other repositories
api-integration-architect
Design, implement, debug, and optimize API integrations with expert-level patterns for REST, GraphQL, webhooks, and authentication flows.
mirrord-db-branching
Helps users configure mirrord.json for database branching, enabling isolated database copies for safe development and testing. Use when the user wants to set up MySQL, MariaDB, PostgreSQL, MSSQL, MongoDB, Redis, DynamoDB, ClickHouse, Google Spanner, Amazon S3, turbopuffer, or generic branches, configure copy modes…
seedance-pipeline
This skill should be used when the user asks about Seedance 2.0 workflow operations, API planning, BytePlus ModelArk, Dreamina/Jimeng surfaces, provider/router APIs, China-facing surfaces, ComfyUI, post-production, stitching, batch workflow, or integration planning.
horse-database-pooling
Guide for setting up thread-safe database connection pooling (FireDAC / UniDAC) in multithreaded Horse applications.
manage-connector
Use when connecting to external data systems for ingestion or export in DataSQRL. Use for Kafka, filesystem, database, Iceberg, or other connector configuration.
unauth-api-flow-hijack
Exploit unauthenticated multi-step API flows without credentials.