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/jikig-ai/soleurWrote 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/jikig-ai/soleur/soleur-engineering-discovery-agent-finder)<a href="https://agentmods.dev/agents/jikig-ai/soleur/soleur-engineering-discovery-agent-finder"><img src="https://agentmods.dev/badge/agents/jikig-ai/soleur/soleur-engineering-discovery-agent-finder/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/agents/jikig-ai/soleur/soleur-engineering-discovery-agent-finder"><img src="https://agentmods.dev/badge/agents/jikig-ai/soleur/soleur-engineering-discovery-agent-finder.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.00068 | $0.00103 |
| Opus 5 | $0.00034 | $0.00051 |
| Sonnet 5 | $0.00014 | $0.00021 |
| Haiku 4.5 | $0.00007 | $0.00010 |
Grade A, and why
soleur-engineering-discovery-agent-finder 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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 · 8 lines · 68 tokens per session scan A 213b970809d6
soleur-engineering-discovery-agent-finder is an agent published in the GitHub repository jikig-ai/soleur (15 stars, last pushed today), with no licence file. It adds 68 tokens to every session and 103 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
cloud-architect
Cloud architect. Delegate only when the user explicitly starts an Octopus workflow.
performance-engineer
Performance engineer. Delegate only when the user explicitly starts an Octopus workflow.
tdd-orchestrator
TDD orchestrator. Delegate only when the user explicitly starts an Octopus workflow.
ccf-codebase-analyzer
Read-only explorer that analyzes ONE slice of an existing codebase and returns a structured report of what exists. Proposes no solutions and writes no files. Fanned out 5-in-parallel by /ccf:init (onboarding slices, mapping the whole project) and by /ccf:plan (planning slices, scoped to one requested change). Use this…
ccf-spec-writer
Drafts CLAUDE.md and .claude/rules/.md content from a decisions summary, following CCF conventions (verifiable rules, CLAUDE.md under 200 lines, @import). Returns proposed file content; the main thread is the one that writes. Used by /ccf:init and /ccf:updatespec.
ccf-best-practice-researcher
Fetches current best practices for given technologies/patterns from Context7 and Microsoft Learn and returns a concise, CITED recommendation. Read-only, and it drafts no spec and writes no files. Used by /ccf:init and /ccf:plan to ground design decisions.