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 foritin/r-code --skill assetsgit clone --depth 1 https://github.com/foritin/r-codeWrote 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/foritin/r-code/assets)<a href="https://agentmods.dev/skills/foritin/r-code/assets"><img src="https://agentmods.dev/badge/skills/foritin/r-code/assets/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/foritin/r-code/assets"><img src="https://agentmods.dev/badge/skills/foritin/r-code/assets.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.00000 | $0.00339 |
| Opus 5.5 | $0.00000 | $0.00136 |
| Sonnet 5.5 | $0.00000 | $0.00068 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
assets 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.
What it actually says
R-Code Collaboration
R-Code can be available as a local MCP server named r-code. Use it only when
the user asks you to delegate a focused investigation to R-Code's own Agent.
Safe delegation flow
- Work only with a
workspace_paththat the user has already opened in R-Code. Do not guess paths or ask R-Code to inspect a different folder. - Call
r_code_delegatewith a concretegoal. Omitaccess, or useaccess: "read_only", unless the user or parent task explicitly authorized edits for this delegated task. - If the result is still running, call
r_code_wait_for_resultorr_code_task_statususing the returnedtask_id. - Use the returned concise result in your answer. A read-only result is not permission to write files, run commands, or delegate additional work.
Capability boundary
The R-Code MCP service creates a read-only task by default. Its Agent can inspect
the already-approved workspace, but cannot edit files, run shell commands,
create terminals, or spawn more agents. Use access: "full_access" only when an
explicit authorization statement from the user or parent task is also supplied
as authorization; R-Code still applies the project's approval policy. The MCP
service never exposes provider credentials or Codex credentials.
Use r_code_cancel_task only to stop a task that this same MCP session started.
Do not attempt to call undocumented terminal.*, ControlDoor, or environment
variable interfaces; they are not part of the R-Code MCP contract.
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 · 30 lines · 0 tokens per session scan A d0b3f474601b
assets is a skill published in the GitHub repository foritin/r-code (2 stars, last pushed 16d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 339 tokens. 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
frontend-best-practices
Coding guidance for building React or Vue front ends, where components display screens and manage user interactions. It covers component responsibilities, state placement, performance, and accessibility.
rust-safety
A guide to writing Rust code around ownership, borrowing, error results, and carefully limited unsafe code.
channels-setup
Use when a developer wants to build their first CopilotKit Channels agent and get it answering in Slack or Microsoft Teams: "set up a channel", "connect my agent to Slack", "get my agent into Teams", or starting from nothing and wanting a working channel end to end. Covers the whole path: inspecting or scaffolding the…
intelligence-vocabulary
Locks customer-facing CopilotKit Intelligence docs to one approved name per concept. Use when writing, editing, or reviewing Intelligence docs, nav labels, signup labels, or image alt text in showcase/shell-docs. Don't use for renaming code identifiers, route slugs, env vars, API fields, or component names, or for…
dashboard-widgets
Author a dashboard widget — a small React component backed by named LangWatchQL queries — from a plain question. Discovers the analytics schema, writes the queries, writes the widget file, saves it, then proves it renders. Use when asked to build, prototype, or iterate on a custom chart widget, or to add a widget…
slacrawl
Archive and search Slack workspace messages, threads, and channels via the slacrawl CLI. Supports API sync, Slack export ZIP import, local desktop cache import, and full-text search.