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 nanoAgentTeam/research-claw --skill conference-researchgit clone --depth 1 https://github.com/nanoAgentTeam/research-clawWrote 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/nanoagentteam/research-claw/conference-research)<a href="https://agentmods.dev/skills/nanoagentteam/research-claw/conference-research"><img src="https://agentmods.dev/badge/skills/nanoagentteam/research-claw/conference-research/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/nanoagentteam/research-claw/conference-research"><img src="https://agentmods.dev/badge/skills/nanoagentteam/research-claw/conference-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00055 | $0.00860 |
| Opus 5 | $0.00028 | $0.00430 |
| Sonnet 5 | $0.00011 | $0.00172 |
| Haiku 4.5 | $0.00006 | $0.00086 |
Grade A, and why
conference-research 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.
How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
[SKILL: CONFERENCE RESEARCH PROTOCOL]
When researching papers from specific academic venues, standard arxiv_search with venue names WILL FAIL — conference names never appear in arXiv paper titles. Use the source-specific strategies below instead.
Source Priority (try in order)
1. NLP Venues: ACL / EMNLP / NAACL / EACL / COLING
ACL Anthology is the authoritative proceedings database for all ACL-family venues.
web_search: site:aclanthology.org "{topic}" {year}
web_search: site:aclanthology.org "{year}.{venue-code}-main"
Venue codes: acl-long, acl-short, emnlp-main, naacl-main, eacl-main
Examples:
- EMNLP 2024 long-document papers →
site:aclanthology.org "long document" 2024.emnlp-main - ACL 2023 RAG papers →
site:aclanthology.org "retrieval augmented" 2023.acl-long
2. ML Venues: NeurIPS / ICLR / ICML
All three now use OpenReview. Do NOT use site:proceedings.mlr.press — it is not well-indexed by web search.
Do NOT quote the topic phrase; use bare keywords:
web_search: site:openreview.net {topic keywords} NeurIPS 2024
web_search: site:openreview.net {topic keywords} ICLR 2024
web_search: site:openreview.net {topic keywords} ICML 2024
Examples:
- NeurIPS 2024 long context papers →
site:openreview.net long context NeurIPS 2024 - ICLR 2025 RAG papers →
site:openreview.net retrieval augmented generation ICLR 2025
3. Systems Venues: MLSys / OSDI / SOSP / EuroSys
Use DBLP:
web_search: site:dblp.org {venue-abbrev} {year} {topic keywords}
If DBLP returns no results, fall back to a plain web search:
web_search: {venue} {year} {topic keywords} accepted papers
4. Cross-Venue Search via Semantic Scholar
web_search: site:semanticscholar.org "{topic}" venue:"{Conference Full Name}"
5. CFP and Acceptance Criteria
To find Call for Papers, review criteria, or scope descriptions:
web_search: "{Conference} {year} call for papers"
web_search: "{Conference} {year} submission guidelines"
web_search: "{Conference} {year} review criteria"
web_search: "{Conference} {year} acceptance rate topics"
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 · 81 lines · 55 tokens per session scan A b058032d1e82
conference-research is a skill published in the GitHub repository nanoAgentTeam/research-claw (292 stars, last pushed 3mo ago), licensed MIT. It adds 55 tokens to every session and 860 once invoked, about $0.0003 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-30.
Other skills, from other repositories
local-llm-tool
Local LLM execution tool for text generation and chat through Ollama or vLLM endpoints. Use when: running on-prem inference, calling a local GPU model, or summarizing with a self-hosted LLM.
sflo
Starts and manages SFLO factory runs through the configured runner. Use when the user explicitly asks to start, run, resume, list, kill, clean, or inspect an SFLO factory, including requests to build something with SFLO. Do not use when SFLO appears only in quoted text, documentation, examples, code, logs, or…
design
Create a doc-as-code design package from a PRD or SPEC. Conditionally generates C4 diagrams (Context/Container/Component), sequence diagrams, ER diagram + Data Dictionary, OpenAPI 3.0, AsyncAPI 3.0, ADRs, domain glossary, state diagrams, and deployment view as Mermaid-rendered Markdown files. Use when PM mentions…
understand-codebase
Understand an unfamiliar codebase or plan a change safely, using Spine's deterministic knowledge-graph MCP tools. Reach for this before answering structural questions about a repo you don't know, before editing code, or when debugging — it hands you engineering decisions (what a change breaks, what's untested, where a…
review-pr
A pull-request review skill for evaluating proposed code changes and posting a quality verdict. A pull request is a request to merge changes into a shared codebase.
tasks
A task-breakdown tool that turns a plan, specification, feature brief, bug report, technical-debt item, or chore into small TASK-NNN work items. Technical debt means postponed cleanup or design work in a codebase.