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 skills add TeamDzX/myllm-skills --skill research-briefgit clone --depth 1 https://github.com/TeamDzX/myllm-skillsWrote 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/skills/teamdzx/myllm-skills/research-brief)<a href="https://agentmods.dev/skills/teamdzx/myllm-skills/research-brief"><img src="https://agentmods.dev/badge/skills/teamdzx/myllm-skills/research-brief/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/skills/teamdzx/myllm-skills/research-brief"><img src="https://agentmods.dev/badge/skills/teamdzx/myllm-skills/research-brief.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.00037 | $0.00252 |
| Opus 5 | $0.00018 | $0.00126 |
| Sonnet 5 | $0.00007 | $0.00050 |
| Haiku 4.5 | $0.00004 | $0.00025 |
Grade A, and why
research-brief 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.
What it actually says
Research brief
Answer the user's question with a concise, sourced brief — not a wall of text.
-
Run
web_searchwith 2–4 focused queries (vary the angle; don't repeat one phrasing). Open the most promising results withfetch_urlwhen you need detail. -
Synthesise across sources. Structure the answer as:
Answer — the direct conclusion in 2–4 sentences.
What the sources say
- Bullet each substantive finding, each followed by its source link.
Confidence & gaps — how solid this is, and what's still uncertain or contested.
Sources
- Title — URL (one per source actually used).
Rules:
- Cite only links that came back from a tool. Never invent or guess a URL.
- Prefer primary/recent sources; flag when sources disagree.
- Date-stamp time-sensitive claims; today's date is authoritative.
- If the tools return nothing usable, say so plainly rather than guessing.
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 · 29 lines · 37 tokens per session scan A f1b1154db84f
research-brief is a skill published in the GitHub repository TeamDzX/myllm-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 252 once invoked, about $0.0002 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 skills, from other repositories
edgeone skill scanner
A local static scanner that checks agent-skill files for security risks before they are installed or used. Static analysis examines files without running them.
avoid-ai-writing
Audit and rewrite content to remove AI writing patterns ("AI-isms"). Use this skill when asked to "remove AI-isms," "clean up AI writing," "edit writing for AI patterns," "audit writing for AI tells," or "make this sound less like AI." Supports a detect-only mode, an edit-in-place mode for files, an optional voice…
preservation-verifier
Use when the user provides an original and rewritten version, asks whether a rewrite preserved protected content, or wants a deterministic check for code, frontmatter, quotes, tables, links, paths, numbers, headings, and residual AI-pattern regressions.
ai-writing-detector
Use when the user asks to detect, scan, audit, score, or flag AI-writing patterns without rewriting the text, including requests for a deterministic local detector result when the host can execute Node.
avoid-ai-writing-router
Use when a request combines AI-writing audit, rewrite, file editing, voice preservation, false-positive interpretation, verification, or when the user invokes Avoid AI Writing without naming a mode.
file-edit-in-place
Use when the user names a local file and explicitly asks to clean, rewrite, humanize, or remove AI-writing patterns in that file itself, with minimal targeted edits and post-edit verification.