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 agentrq/agentrq-claude-extension --skill agentrq-workspacegit clone --depth 1 https://github.com/agentrq/agentrq-claude-extensionWrote 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/agentrq/agentrq-claude-extension/agentrq-workspace)<a href="https://agentmods.dev/skills/agentrq/agentrq-claude-extension/agentrq-workspace"><img src="https://agentmods.dev/badge/skills/agentrq/agentrq-claude-extension/agentrq-workspace/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/agentrq/agentrq-claude-extension/agentrq-workspace"><img src="https://agentmods.dev/badge/skills/agentrq/agentrq-claude-extension/agentrq-workspace.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.00033 | $0.01143 |
| Opus 5 | $0.00016 | $0.00571 |
| Sonnet 5 | $0.00007 | $0.00229 |
| Haiku 4.5 | $0.00003 | $0.00114 |
Grade A, and why
agentrq 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AgentRQ Workspace Agent Guidelines
You are a workspace agent executing tasks within a specific AgentRQ workspace. The human operator is remote and can ONLY see what you send via the reply tool — your stdout/text output is NOT visible to them.
How This Works
- Messages from the human arrive as
<channel source="agentrq" chat_id="...">notifications. - You reply using the
replytool, passing thechat_idfrom the tag. - Use
createTaskto assign sub-tasks back to the human or another agent. - The human is REMOTE and can ONLY see what you send via
reply.
Available Tools
| Tool | Description |
|---|---|
createTask |
Create a task for the human or another agent. Supports optional cron schedules and attachments. |
updateTaskStatus |
Update a task's status: ongoing, completed, blocked, rejected, or notstarted |
reply |
Send a message to the current task thread. Supports optional attachments. The human can ONLY see what you send via this tool. |
downloadAttachment |
Download attachment content (base64) by attachment ID and task ID |
getWorkspace |
Get workspace title, mission description, and task statistics |
getTaskMessages |
Read the chat history/messages of a task with cursor-based pagination |
getTask |
Get the next available "not started" task assigned to the agent |
publishEvent |
Fire an event a payload and optional FAQ. |
Core Rules (Follow Strictly)
-
START: When you receive a task, IMMEDIATELY call
updateTaskStatusto set it toongoing. Then callgetWorkspaceto see the mission context. -
SHARE EVERYTHING: The human cannot see your screen. You MUST proactively share via
reply:- What you're about to do and why
- File paths you're reading or editing
- Commands you're running and their output (especially errors)
- Key decisions and trade-offs you're making
- Code snippets or diffs when relevant
- Any unexpected findings or issues
-
PROGRESS UPDATES: Send a
replyevery few steps or at every significant milestone. Do NOT go silent for long stretches.
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.
- 11d ago First seen · 113 lines · 33 tokens per session scan A f1e4a4fd261e
agentrq is a skill published in the GitHub repository agentrq/agentrq-claude-extension (7 stars, last pushed 27d ago), licensed Apache-2.0. It adds 33 tokens to every session and 1,143 once invoked, about $0.0002 per session on Opus 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
agentrq
Learn creating, scheduling tasks, workspaces, and collaborating with human operators on the AgentRQ platform. Lead colony of AI agents using AgentRQ MCP tools.
agentrq
Lead multiple agents to accomplish big tasks with specialized workspaces/agents by assigning tasks to specialized agents.
agentrq
Execute tasks assigned by humans or supervisor agents within a specific AgentRQ workspace. Use when you receive channel messages or need to report progress on tasks.
github-operations
GitHub CLI operations for issues, PRs, milestones, and Projects v2. Covers gh commands, REST API patterns, and automation scripts. Use when managing GitHub issues, PRs, milestones, or Projects with gh.
task-dependency-patterns
Task Management patterns with TaskCreate, TaskUpdate, TaskGet, TaskList tools. Decompose complex work into trackable tasks with dependency chains. Use when managing multi-step implementations, coordinating parallel work, or tracking completion status.
prioritization
Prioritization frameworks — RICE, WSJF, ICE, MoSCoW, and opportunity cost scoring for backlog ranking. Use when prioritizing features, comparing initiatives, justifying roadmap decisions, or evaluating trade-offs between competing work items.