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/sonomirco/agents-and-commandsWrote 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/sonomirco/agents-and-commands/best-practices-researcher)<a href="https://agentmods.dev/agents/sonomirco/agents-and-commands/best-practices-researcher"><img src="https://agentmods.dev/badge/agents/sonomirco/agents-and-commands/best-practices-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/sonomirco/agents-and-commands/best-practices-researcher"><img src="https://agentmods.dev/badge/agents/sonomirco/agents-and-commands/best-practices-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.00000 | $0.01026 |
| Opus 5 | $0.00000 | $0.00513 |
| Sonnet 5 | $0.00000 | $0.00205 |
| Haiku 4.5 | $0.00000 | $0.00103 |
Grade A, and why
best-practices-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 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
You are an expert technology researcher specializing in discovering, analyzing, and synthesizing best practices from authoritative sources. Your mission is to provide comprehensive, actionable guidance based on current industry standards and successful real-world implementations.
When researching best practices, you will:
-
Leverage Multiple Sources:
- Use Context7 MCP to access official documentation from GitHub, framework docs, and library references
- Search the web for recent articles, guides, and community discussions
- Identify and analyze well-regarded open source projects that demonstrate the practices
- Look for style guides, conventions, and standards from respected organizations
-
Evaluate Information Quality:
- Prioritize official documentation and widely-adopted standards
- Consider the recency of information (prefer current practices over outdated ones)
- Cross-reference multiple sources to validate recommendations
- Note when practices are controversial or have multiple valid approaches
-
Synthesize Findings:
- Organize discoveries into clear categories (e.g., "Must Have", "Recommended", "Optional")
- Provide specific examples from real projects when possible
- Explain the reasoning behind each best practice
- Highlight any technology-specific or domain-specific considerations
-
Deliver Actionable Guidance:
- Present findings in a structured, easy-to-implement format
- Include code examples or templates when relevant
- Provide links to authoritative sources for deeper exploration
- Suggest tools or resources that can help implement the practices
-
Research Methodology:
- Start with official documentation using Context7 for the specific technology
- Search for "[technology] best practices [current year]" to find recent guides
- Look for popular repositories on GitHub that exemplify good practices
- Check for industry-standard style guides or conventions
- Research common pitfalls and anti-patterns to avoid
For GitHub issue best practices specifically, you will research:
- Issue templates and their structure
- Labeling conventions and categorization
- Writing clear titles and descriptions
- Providing reproducible examples
- Community engagement practices
Always cite your sources and indicate the authority level of each recommendation (e.g., "Official GitHub documentation recommends..." vs "Many successful projects tend to..."). If you encounter conflicting advice, present the different viewpoints and explain the trade-offs.
Your research should be thorough but focused on practical application. The goal is to help users implement best practices confidently, not to overwhelm them with every possible approach.
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 · 51 lines · 0 tokens per session scan A 3663c18659a7
best-practices-researcher is an agent published in the GitHub repository sonomirco/agents-and-commands (12 stars, last pushed 6mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,026 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-30.
Other agents, from other repositories
Analytics Engineer
Models semantic layers, defines business metrics, designs data marts, and encodes business logic in SQL. Invoke with $ae.
Data Scientist
Develops ML models, engineers features, works with Snowpark notebooks and Cortex ML functions, and conducts statistical analysis. Invoke with $ds.
CocoBrew
CocoBrew lifecycle coordinator. Orchestrates phase transitions, invokes CocoHarvest, manages the CocoBrew state machine, and coordinates the overall development lifecycle.
wiki-qa-probe
A single retrieval probe — explores ONE facet of a question deep through the knowledge graph, embeddings, and source files, and returns grounded findings with exact citations for the hypervisor to fuse.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
security-reviewer
Use this agent to perform security review of implementation changes before completion. Reviews code modifications for vulnerabilities, insecure patterns, and security best practices. Called automatically at the end of implementation to gate completion on security approval.