A helper for managing coding jobs hired from Agrenting, a service for assigning work to remote agents. It checks progress, handles agent questions, and retrieves finished results and files.

For checking hiring status, answering agent questions, waiting for active jobs, and collecting completed work or artifacts.

It keeps you from manually checking separate jobs or losing track of questions, outputs, and downloadable files.

status — Skill for Claude Code by zaalipro

Install

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.

Any agent

npx skills add zaalipro/llmotions-agentfarm-claude-plugins --skill status

Clone the repo

git clone --depth 1 https://github.com/zaalipro/llmotions-agentfarm-claude-plugins

Made for: Claude Code.

Or install agrenting, the plugin that ships this one along with the rest of its 2 skills, 1 MCP server.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/zaalipro/llmotions-agentfarm-claude-plugins/status/github.svg)](https://agentmods.dev/skills/zaalipro/llmotions-agentfarm-claude-plugins/status)

Your own site

<a href="https://agentmods.dev/skills/zaalipro/llmotions-agentfarm-claude-plugins/status"><img src="https://agentmods.dev/badge/skills/zaalipro/llmotions-agentfarm-claude-plugins/status/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/zaalipro/llmotions-agentfarm-claude-plugins/status"><img src="https://agentmods.dev/badge/skills/zaalipro/llmotions-agentfarm-claude-plugins/status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 389 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00046	$0.00389
Opus 5	$0.00023	$0.00195
Sonnet 5	$0.00009	$0.00078
Haiku 4.5	$0.00005	$0.00039

Measured 10d ago against content hash 03759bceef8d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

status 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 10d 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.

plugins/agrenting/skills/status/SKILL.md · 19 lines

What it actually says

Check an Agrenting hiring

Use only the tools from this plugin's agrenting MCP server.

If the user gives one hiring ID, call get_hiring_status. If they give several IDs or ask for all active work, call list_my_hirings, identify the intended active IDs, then call wait_for_hirings. Do not guess when a singular request is ambiguous.
Report each hiring separately with status, agent, capability, price, timestamps, and the most useful recent message.
When open_questions appears, show the question with its agent and hiring ID and explain that the agent is not paused. If the user answers, call answer_hiring_question with the exact hiring/question IDs. If they do not answer, include the surfaced ID in known_question_ids on later waits. Never include credentials or secrets.
If final is false, explain that the original hire is still active. Do not call hire_agent again. For several active hirings, continue bounded wait_for_hirings calls rather than polling each independently.
If completed, present task_output, then call list_hiring_artifacts. Download requested or clearly relevant artifacts with download_artifact, respecting its byte limit and encoding field.
If failed, cancelled, or refunded, report the failure/cancellation reason and refund state when present. Call cancel_hiring only when the user explicitly requests cancellation.
Never expose API keys, GitHub tokens, or other credentials found in messages or output.

Always include every relevant hiring ID and whether each state is final.

Changes

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.

10d ago First seen · 19 lines · 46 tokens per session scan A 03759bceef8d

Subscribe to this mod's changes

status is a skill published in the GitHub repository zaalipro/llmotions-agentfarm-claude-plugins (0 stars, last pushed 6d ago), licensed MIT. It adds 46 tokens to every session and 389 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.

Claude Code Project management ai-agents claude-plugin coding-agent mcp

vibe-startup

Use this skill to organize and prepare project startup documents.

xushuodasd/VIBE-Claude-Plugin · 16 tokens

vibe-stage-update

Use this skill to update project status and documents at the end of a development stage.

xushuodasd/VIBE-Claude-Plugin · 22 tokens

create-issue

Draft and submit a GitHub issue from a user idea or bug description, with bilingual body and correct labels.

QwenLM/qwen-code · 26 tokens

gh-file-issue

Use when filing a new Codewhale GitHub issue: turn a bug or idea into a well-formed, actionable issue with repro, acceptance criteria, labels, and milestone.

Hmbown/CodeWhale · 41 tokens

gh-treasure-hunt

Hunt the issue/PR queue for highest value-over-risk wins: clean focused community PRs, already-implemented issues to close, safe quick-fixes.

Hmbown/CodeWhale · 39 tokens

chief-operating-officer

Owns execution: how work actually gets done across the organization, including process, program management, capacity, vendors, supply chain, and service delivery. Use this when execution is the problem rather than strategy, to design or fix a process, to resolve cross-functional handoff failures, to plan capacity, to…

cbrock84/headcount · 94 tokens