help-reader

A test agent that reads the Context help index and then retrieves the full help text for one topic.

In plain words
What is it for?
Use it to verify Context.help and confirm that a specific documentation topic, such as scopes, is available.
Why use it?
It checks that the help system can list available topics and return detailed documentation for a selected topic.

Agent

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.

agentmods
npx agentmods add agents/denn-gubsky/loomcycle/help-reader
Clone the repo
git clone --depth 1 https://github.com/denn-gubsky/loomcycle
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 273 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00014 $0.00273
Opus 5 $0.00007 $0.00137
Sonnet 5 $0.00003 $0.00055
Haiku 4.5 $0.00001 $0.00027

Measured 2d ago against content hash fbc5a28c1389, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

help-reader 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 2d 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.

test/runtime/context-help/agents/help-reader.md · 31 lines

What it actually says

You are help-reader. Your job is to discover loomcycle's help system by calling Context.help twice, then write a one-line summary.

Rules:

  1. Make EXACTLY two Context tool calls, in this order: (1) op=help — list all available topics (2) op=help, topic=scopes — fetch the scopes topic's full body

  2. After BOTH help calls complete, write a one-line summary that includes:

    • the number of topics you saw in the index (from call 1)
    • the name of one topic that appeared in the index
    • one short phrase you actually read from the scopes topic body (from call 2) — quote a substring of the markdown content

    End the summary with the single word DONE.

  3. Do not call any other tool besides Context. The agent's tools is deliberately empty — the runtime auto-attaches Context via v0.8.7 default-add. If you see "Context tool not available" or "help: not configured", report that and end with DONE.

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.

  1. 2d ago First seen · 31 lines · 14 tokens per session scan A fbc5a28c1389

Subscribe to this mod's changes

help-reader is an agent published in the GitHub repository denn-gubsky/loomcycle (13 stars, last pushed 3d ago), licensed Apache-2.0. It adds 14 tokens to every session and 273 once invoked, about $0.0001 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-30.

Related

Other agents, from other repositories

implementer

The Implementer agent receives a plan from the Planner and executes it step by step. It uses the WorkspaceTools (readfile, listfiles, searchcode, applydiff) to inspect context and apply file changes.

strikersam/autonomous-ai-agency · 0 tokens

Audit

Deep security + performance audit of a specific diff. Wraps /skill:security-hardening and /skill:performance-optimization (analysis phase only). Use when a change touches auth, untrusted input, secrets, webhooks, PII, or a latency/throughput budget — a focused, read-only risk pass that returns findings the parent…

BlackBeltTechnology/pi-agent-dashboard · 98 tokens

proposal-writer

Specialized agent for generating professional, branded proposals using a presentation-generation tool. Creates polished presentations and documents for sales opportunities from your project and CRM context.

Zeekeey-jpeg/LeRoy-HQ · 34 tokens

juez-filosofia

Guardián de las seis ideas centrales y los ADRs. Audita propuestas de diseño (nueva sesión S##, resolución de un G##, adición a api.md), no diffs de código rutinarios. Su misión es frenar el API creep y la contaminación del kernel con vocabulario de producto. Lanzar desde las skills planificar-sesion y hallazgo.

dbareagimeno/enu · 83 tokens

chronology-builder

Isolated worker that reads case documents iteratively and extracts sourced timeline events (date, neutral fact, mandatory document+locus provenance, undisputed/alleged/contested status, party attribution). Deduplicates and cross-references across documents and languages. Emits events.json for the legal-chronology…

fedec65/bettercallclaude · 103 tokens

flutter-forge

You are Flutter Forge, a specialized Flutter/Dart code generation agent trained on your mobile app patterns and your project standards.

vikisingh23/neuraforge-ai · 0 tokens