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 agentmods add agents/configflux/weld/plannergit clone --depth 1 https://github.com/configflux/weldWhat 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 | $0.00010 | $0.00029 |
| Opus 5 | $0.00005 | $0.00015 |
| Sonnet 5 | $0.00002 | $0.00006 |
| Haiku 4.5 | $0.00001 | $0.00003 |
Grade A, and why
planner 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.
The source is not reproduced here
Licensed Apache-2.0
The repository is licensed Apache-2.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 2d ago First seen · 7 lines · 10 tokens per session scan A cbb21bf1748b
planner is an agent published in the GitHub repository configflux/weld (6 stars, last pushed 2d ago), licensed Apache-2.0. It adds 10 tokens to every session and 29 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-31.
Other agents, from other repositories
architecture-review
Performs architectural review of files undergoing large-scale updates. Use proactively when refactoring, restructuring modules, or reviewing code organization. Provides actionable suggestions for renaming, moving functions, and restructuring modules.
lesson-learner
Use proactively when the user asks to encode insights or guidelines into CLAUDE.md. Triggers include phrases like "update your memory", "remember to do this", "learn from this", or "add this to the guidelines". Extracts generalizable principles from context and proposes targeted improvements to project documentation.
test-coverage-analyzer
Analyzes test coverage for a change set by reading source and test files, identifying which functions/modules have tests, and reporting coverage gaps. Use when reviewing PRs, before completing features, or when asked to check test coverage.
triage-investigator
Investigates a single entry point candidate to determine if it is a true positive, dead code, or a false positive that Ariadne missed callers for. Returns a TriageEntryResult JSON.
backlog-navigator
Researches the backlog to find incomplete tasks, recently completed tasks, and suggests the most likely next task candidates based on dependencies, priorities, and completion patterns. Use when starting work sessions or deciding what to work on next.
plan-reviewer
Reviews a synthesized fix plan from a specific angle (info-architecture, simplicity, fundamentality, or language-coverage). Writes review to a file.