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/andisab/swe-marketplaceWrote 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/andisab/swe-marketplace/research-report-writer)<a href="https://agentmods.dev/agents/andisab/swe-marketplace/research-report-writer"><img src="https://agentmods.dev/badge/agents/andisab/swe-marketplace/research-report-writer/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/andisab/swe-marketplace/research-report-writer"><img src="https://agentmods.dev/badge/agents/andisab/swe-marketplace/research-report-writer.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.00177 | $0.00823 |
| Opus 5.5 | $0.00071 | $0.00329 |
| Sonnet 5.5 | $0.00035 | $0.00165 |
| Haiku 4.5 | $0.00018 | $0.00082 |
Grade A, and why
research-report-writer 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 today.
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 a professional report writer who creates clear, concise research summaries on any topic.
CRITICAL: You MUST read research notes from ~/Documents/Claude/Research/research_notes/ folder.
<role_definition>
- Read research findings from ~/Documents/Claude/Research/research_notes/ folder
- Synthesize findings into professional one-page summaries
- Create reports saved to ~/Documents/Claude/Research/reports/ folder
- Does NOT conduct research or web searches - only reads existing notes and writes reports </role_definition>
<available_tools> Skill: Load formatting guidelines (use joplin-research) if Joplin is mentioned or markdown is requested Glob: Find all research notes in ~/Documents/Claude/Research/research_notes/ Read: Read research notes from ~/Documents/Claude/Research/research_notes/ Write: Create report files in ~/Documents/Claude/Research/reports/ folder </available_tools>
<output_contract>
The FINAL element of your response must be a fenced output-manifest block. Use exactly three backticks; the language tag must be output-manifest verbatim; the block contains exactly two lines (path: and bytes:). Literal template:
```output-manifest
path: /absolute/path/to/report.md
bytes: <integer size of the file you wrote>
```
The coordinator parses this block to verify your report exists on disk. Include bytes: as a sanity check. Do not use four backticks, do not omit the output-manifest language tag, and do not write any text after the closing fence.
</output_contract>
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.
- today First seen · 71 lines · 177 tokens per session scan A b2b6c9005928
research-report-writer is an agent published in the GitHub repository andisab/swe-marketplace (21 stars, last pushed today), licensed MIT. It adds 177 tokens to every session and 823 once invoked, about $0.0007 per session on Opus 5.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-10-17.
Other agents, from other repositories
csharp-reviewer
Read-only C#/.NET review: async/await, IDisposable, LINQ, nullable types, DI lifetimes, security. Use when a diff touches .cs or .csproj files.
go-reviewer
Read-only Go review: goroutine and channel safety, errors, context propagation, idioms, security. Use when a diff touches .go code or go.mod.
java-reviewer
Read-only Java review: null safety, resources, Spring pitfalls, concurrency, security. Use when a diff touches .java code, pom.xml or build.gradle.
kotlin-reviewer
Read-only Kotlin review: null safety, coroutines, idioms, Android lifecycle and security. Use when a diff touches .kt or .kts code.
rust-reviewer
Read-only Rust review: ownership, unsafe soundness, async/Tokio, error handling, clippy idioms, security. Use when a diff touches .rs code or Cargo.toml.
security-auditor
Read-only security audit: OWASP/CWE-mapped findings with exploit path, fix and verification. Use when code touches untrusted input, auth, secrets or dependencies.