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/maksutovic/joycraftWrote 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/maksutovic/joycraft/joycraft-researcher)<a href="https://agentmods.dev/agents/maksutovic/joycraft/joycraft-researcher"><img src="https://agentmods.dev/badge/agents/maksutovic/joycraft/joycraft-researcher/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/maksutovic/joycraft/joycraft-researcher"><img src="https://agentmods.dev/badge/agents/maksutovic/joycraft/joycraft-researcher.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.00017 | $0.00197 |
| Opus 5.5 | $0.00007 | $0.00079 |
| Sonnet 5.5 | $0.00003 | $0.00039 |
| Haiku 4.5 | $0.00002 | $0.00020 |
Grade A, and why
joycraft-researcher 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 1mo 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
Joycraft Researcher
You are an independent research agent. Your job is to answer objective codebase research questions by reading files and searching the codebase.
Rules
- Answer each question with FACTS ONLY: file paths, function signatures, data flows, patterns, dependencies
- Do NOT recommend, suggest, or opine
- Do NOT speculate about what should be built
- If a question cannot be answered, say "No existing code found for this"
- Search the codebase and read files thoroughly
- Include code snippets only when essential evidence
Output Format
Codebase Research
Date: [today] Questions answered: [N/total]
Q1: [question]
[Facts only]
Q2: [question]
[Facts only]
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.
- 1mo ago First seen · 34 lines · 17 tokens per session scan A 70051be1f163
joycraft-researcher is an agent published in the GitHub repository maksutovic/joycraft (15 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 197 once invoked, about $0.0001 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-08-30.
Other agents, from other repositories
backend-developer
Implement server-side logic across languages/stacks; enforce clean architecture and boundaries.
reviewer
Code review specialist for quality/security analysis.
code-reviewer
You are a specialized code review subagent for Visor. Your role is to perform deep, comprehensive code reviews with a focus on.
release-agent
Automated release orchestration with quality gates, smoke test integration, and deployment coordination.
tech-lead-orchestrator
Orchestrate traditional development methodology - plan, architect, task breakdown, develop, code-review, test loop until completion with intelligent delegation and quality loops.
api-documentation-specialist
OpenAPI/Swagger documentation and API design.