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.
git clone --depth 1 https://github.com/Gary06868/remote-agent-collaboration-skillsWrote 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/plugins/gary06868/remote-agent-collaboration-skills/remote-agent-collaboration-lite)<a href="https://agentmods.dev/plugins/gary06868/remote-agent-collaboration-skills/remote-agent-collaboration-lite"><img src="https://agentmods.dev/badge/plugins/gary06868/remote-agent-collaboration-skills/remote-agent-collaboration-lite.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
remote-agent-collaboration-lite 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 8d 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
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "remote-agent-collaboration-lite",
"displayName": "Remote Agent Collaboration Lite",
"version": "0.7.0",
"description": "Markdown collaboration for small human and AI teams. Installs two skills: team-lead-collaboration and team-member-collaboration.",
"author": {
"name": "Gary06868",
"url": "https://github.com/Gary06868"
},
"homepage": "https://github.com/Gary06868/remote-agent-collaboration-skills",
"repository": "https://github.com/Gary06868/remote-agent-collaboration-skills",
"license": "MIT",
"keywords": [
"claude-code",
"skills",
"collaboration",
"markdown",
"ai-agents",
"vibe-coding"
]
}
What it installs
The manifest is a name and a version. 2 skills travel with it, and installing the plugin installs all of them — 59 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 8d ago First seen · 23 lines scan A d2153b27c97a
remote-agent-collaboration-lite is a plugin published in the GitHub repository Gary06868/remote-agent-collaboration-skills (3 stars, last pushed 2mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
infoops
Codex and OpenClaw compatible InfoOps skill for turning workstream signals into structured operational awareness and action priorities.
rosetta-light
Rosetta for Claude - Software Engineering Accelerator instruction set, workflows, and guardrails. (lightweight: simpler workflows, smaller models).
specrails
SpecRails Agent Workflow System — product-driven AI development pipeline. Installs 14 specialized agents and 20+ workflow skills: /specrails:implement, /specrails:setup, /specrails:get-backlog-specs, and more.
weft
Deterministic workflow tracking with event-sourced logs for Claude Code.
turnstile
Opinionated, gated workflow for solo development with Claude: conversate, brainstorm, refine, breakdown, spec, sprint-plan, work, and review epics, stories, and tasks on a file-based board, plus independent debugging and code review, with a persistent, Obsidian-linked knowledge brain.
recursive-spine
GitHub issues+milestones tracking convention and project spine: recursive-spine-method, recursive-spine-bootstrap, recursive-spine-migrate, recursive-spine-digest, recursive-spine-pollinate, recursive-spine-scaffold, recursive-spine-handover, recursive-spine-nudge. State lives where it's queryable, not where it merges.