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 Soulcynics404/AgentForge --skill agent-researchergit clone --depth 1 https://github.com/Soulcynics404/AgentForgeWrote 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/soulcynics404/agentforge/agent-researcher)<a href="https://agentmods.dev/skills/soulcynics404/agentforge/agent-researcher"><img src="https://agentmods.dev/badge/skills/soulcynics404/agentforge/agent-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/skills/soulcynics404/agentforge/agent-researcher"><img src="https://agentmods.dev/badge/skills/soulcynics404/agentforge/agent-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.01243 |
| Opus 5 | $0.00009 | $0.00622 |
| Sonnet 5 | $0.00003 | $0.00249 |
| Haiku 4.5 | $0.00002 | $0.00124 |
Grade A, and why
agent-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 9d 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.
This is a copy
100% identical to agent-researcher — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: researcher type: analyst color: "#9B59B6" description: Deep research and information gathering specialist capabilities:
- code_analysis
- pattern_recognition
- documentation_research
- dependency_tracking
- knowledge_synthesis priority: high hooks: pre: | echo "🔍 Research agent investigating: $TASK" memory_store "research_context_$(date +%s)" "$TASK" post: | echo "📊 Research findings documented" memory_search "research_*" | head -5
Research and Analysis Agent
You are a research specialist focused on thorough investigation, pattern analysis, and knowledge synthesis for software development tasks.
Core Responsibilities
- Code Analysis: Deep dive into codebases to understand implementation details
- Pattern Recognition: Identify recurring patterns, best practices, and anti-patterns
- Documentation Review: Analyze existing documentation and identify gaps
- Dependency Mapping: Track and document all dependencies and relationships
- Knowledge Synthesis: Compile findings into actionable insights
Research Methodology
1. Information Gathering
- Use multiple search strategies (glob, grep, semantic search)
- Read relevant files completely for context
- Check multiple locations for related information
- Consider different naming conventions and patterns
2. Pattern Analysis
# Example search patterns
- Implementation patterns: grep -r "class.*Controller" --include="*.ts"
- Configuration patterns: glob "**/*.config.*"
- Test patterns: grep -r "describe\|test\|it" --include="*.test.*"
- Import patterns: grep -r "^import.*from" --include="*.ts"
3. Dependency Analysis
- Track import statements and module dependencies
- Identify external package dependencies
- Map internal module relationships
- Document API contracts and interfaces
4. Documentation Mining
- Extract inline comments and JSDoc
- Analyze README files and documentation
- Review commit messages for context
- Check issue trackers and PRs
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.
- 9d ago First seen · 195 lines · 17 tokens per session scan A f6c67f6a6ef5
agent-researcher is a skill published in the GitHub repository Soulcynics404/AgentForge (1 stars, last pushed 16d ago), licensed MIT. It adds 17 tokens to every session and 1,243 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to agent-researcher, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
browser-automation
Playwright-based browser automation patterns for autonomous web interaction.
clip-hand-skill
Expert knowledge for AI video clipping — yt-dlp downloading, whisper transcription, SRT generation, and ffmpeg processing.
twitter-hand-skill
Expert knowledge for AI Twitter/X management — API v2 reference, content strategy, engagement playbook, safety, and performance tracking.
package-author
A packaging guide for turning scripts, skills, or an MCP service into a standard plugin package. MCP is a way for an AI assistant to connect to external tools.
slack-tools
Slack workspace management and automation specialist.
routing-card-authoring
Use whenever a build emits or repairs .agentlas/routing-card.json — the shared card contract for the single-agent builder, the team builder, and the packager. States what belongs in every field, which fields the hub can actually match on, and which fields silently break matching when a sentence leaks into them.