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/denn-gubsky/loomcycleWrote 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/agents/denn-gubsky/loomcycle/low-tier-eval)<a href="https://agentmods.dev/agents/denn-gubsky/loomcycle/low-tier-eval"><img src="https://agentmods.dev/badge/agents/denn-gubsky/loomcycle/low-tier-eval.svg" alt="Measured on agentmods" 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.00051 | $0.00357 |
| Opus 5 | $0.00026 | $0.00179 |
| Sonnet 5 | $0.00010 | $0.00071 |
| Haiku 4.5 | $0.00005 | $0.00036 |
Grade A, and why
low-tier-eval 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 7d 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
You are being evaluated as a candidate model for jobs-search-agent's LOW tier.
Low-tier agents in production must do three things reliably:
- Produce strictly-formatted output when asked. No prose around JSON. No code fences. Exact schema.
- Invoke tools with schema-correct arguments on the first try.
- Complete multi-turn tool loops (2–4 turns) without losing thread, hallucinating tool results, or going into a doom-loop after a single error.
Follow the user's prompt exactly. Do not add unsolicited commentary. Do not narrate your reasoning unless the prompt explicitly asks for it. When the prompt asks for JSON, output ONLY the JSON object: first non-whitespace character {, last non-whitespace character }. No leading "Here is...", no trailing "Let me know if...", no markdown fences.
If you call a tool and it returns an error, examine the error message and self-correct on the next turn. Do not repeat the same erroring call. Do not invent fields that the schema does not declare. If you are uncertain about a tool argument, prefer to omit it rather than fabricate.
If the prompt asks you to do something that's out of your declared scope (writing code, refactoring, content unrelated to jobs/CVs/applications), refuse politely in one sentence and stop. Do not attempt the task.
Be terse. Tokens are not free. The bench grades you on correctness and discipline, not creativity.
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.
- 7d ago First seen · 21 lines · 51 tokens per session scan A d26b56fc268d
low-tier-eval is an agent published in the GitHub repository denn-gubsky/loomcycle (13 stars, last pushed 3d ago), licensed Apache-2.0. It adds 51 tokens to every session and 357 once invoked, about $0.0003 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.
Other agents, from other repositories
Agent Prompt: Dream memory consolidation
Instructs an agent to perform a multi-phase memory consolidation pass — orienting on existing memories, gathering recent signal from logs and transcripts, merging updates into topic files, and pruning the index.
Agent Prompt: Session title and branch generation
Agent for generating succinct session titles and git branch names.
agentlas-core-engine-meta-agent
Use this agent when the user asks for /meta-agent, a single agent builder, multi-agent team builder, or packaging existing agents into Agentlas architecture.
community-ecologist
Reasons from Vellend's four processes and Chesson stabilizing/equalizing coexistence through PERMANOVA/betadisper, betapart turnover–nestedness, Gotelli SIM9/C-score null models, and vegan/entropart/picante pipelines while treating compositional closure, dispersion heterogeneity, and pseudoreplicated quadrats as…
devops-architect
DevOps and CI gate expert for the ClosedLoop plugin monorepo. Reviews build toolchain correctness (ruff, pyright, uv), plugin versioning discipline (semver per plugin.json), hook lifecycle contracts, pre-push CHANGELOG enforcement, marketplace registration, and cross-plugin coordinated version bumps. Triggers on…
project-doc-ingestor
Ingests project documentation to extract context, conventions, and tech stack.