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/megamen32/gptadmin_opensource/reviewergit clone --depth 1 https://github.com/megamen32/gptadmin_opensourceWhat 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.00000 | $0.00336 |
| Opus 5 | $0.00000 | $0.00168 |
| Sonnet 5 | $0.00000 | $0.00067 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
Reviewer 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 AGPL-3.0
The repository is licensed AGPL-3.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 · 31 lines · 0 tokens per session scan A 12b70ac8e1f8
Reviewer is an agent published in the GitHub repository megamen32/gptadmin_opensource (10 stars, last pushed 24d ago), licensed AGPL-3.0. It costs nothing until one of its globs matches a file; then it loads 336 tokens. 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
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
lanes-link-scout
Use when answering a question needs a wide read across someone's Lanes Link context — searching their memory, tasks, files, mail, and issues for the same thing and reporting back what is there. Good for "have I discussed X anywhere", "find everything about this client", "what do we already know about Y". Not for…
triage-labels
The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.
researcher
Use this agent when the user wants to research a topic and get a grounded, cited answer from the web. Typical triggers include "research X for me", "find and index information about X", asking a question where the current index likely has no relevant content, or when a previous ask returned sparse or empty results.…
issue-tracker
Issues and PRDs for this repo live as GitHub issues in YosefHayim/ebay-mcp. Use the gh CLI for issue-tracker operations.
insights-analyst
Read-only analytics and reporting agent that pulls post and account metrics and post history across platforms via Ayrshare, and summarizes performance; never publishes, comments, messages, or modifies anything.