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 poco-ai/Agentero --skill author-lookupgit clone --depth 1 https://github.com/poco-ai/AgenteroWrote 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/poco-ai/agentero/author-lookup)<a href="https://agentmods.dev/skills/poco-ai/agentero/author-lookup"><img src="https://agentmods.dev/badge/skills/poco-ai/agentero/author-lookup/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/poco-ai/agentero/author-lookup"><img src="https://agentmods.dev/badge/skills/poco-ai/agentero/author-lookup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 8 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 63 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 65 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 69 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 70 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 82 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 83 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 89 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 91 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00100 | $0.03846 |
| Opus 5 | $0.00050 | $0.01923 |
| Sonnet 5 | $0.00020 | $0.00769 |
| Haiku 4.5 | $0.00010 | $0.00385 |
Grade A, and why
author-lookup scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
> **工具选择**：本地无爬虫时用 Agent 的联网工具（WebFetch / WebSearch）而非裸 curl； How it starts
The opening of the file, as written. The whole thing — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
作者信息与外链检索
为论文补齐可联系入口与外部链接：一作与通讯作者的 email / 个人主页 / GitHub，以及该 论文的 OpenReview 页面。每条结果都要给出来源；查不到就留空，绝不臆造邮箱、主页或账号。
输入（Agentero vault）
- 目标是
papers/下的论文文件夹（Vault 相对路径，如papers/1706.03762）。 - 先读本地资料，拿到检索线索（标题、作者、DOI、arXiv id）：
- 本地 PDF：首页作者块常带 email 与机构；通讯作者常标
*/†/ “Corresponding author”。 source/**/*.{tex,ltx}：\author、\thanks{...}、\email{...}、\corresponding等宏常含邮箱。{paper}/PAPER.md、{paper}/NOTES.md：已有标题 / DOI / arXiv id 可直接喂给下面的 API。
- 本地 PDF：首页作者块常带 email 与机构；通讯作者常标
- 不要删除或改写
marks/、source/、assets/、attachments/及二进制文件。
需要产出的字段
- 一作（first author）：姓名 + email + homepage + GitHub + ORCID + OpenReview 主页。
- 通讯作者（corresponding author）：同上字段。
- 论文未标注通讯作者时写「文中未标注」，不要拿一作顶替。
- 一作与通讯为同一人时合并说明。
- OpenReview 论文链接：该论文
https://openreview.net/forum?id=...页面（无则写「未找到」）。
各字段检索手段（含 URL / API）
约定：
{TITLE}= 论文标题，{NAME}= 作者姓名，{DOI}、{ARXIV}为对应标识。 调 API 时优先带上标题 / DOI 精确匹配，命中后再核对作者列表一致，避免同名误配。工具选择：本地无爬虫时用 Agent 的联网工具（WebFetch / WebSearch）而非裸 curl； 有反爬（Cloudflare challenge / 302）的站点（OpenReview、Papers with Code）尤其如此。
基线管线（推荐）：先用 OpenAlex（免费、无 key、最稳）把论文映射到作者：
title→authorships[].author{ id, orcid, ... }，拿到 作者 id + ORCID + 机构； 再据机构去作者主页找 email，据 ORCID / GitHub 补链接。其它源作交叉验证或兜底。可靠性备忘（实测）：OpenAlex / DBLP / ORCID / GitHub API 稳定可直调； Semantic Scholar 无 key 易
429（降为副源）；Crossref 的query.bibliographic是模糊匹配（可能返回别的论文），必须核对标题或改用 DOI 直引； Papers with Code API 已失效（302 跳转），不要依赖；OpenReview API 常被 challenge 拦截（403），改走 Web 检索（见下）。
1. Email（最优先取论文原文）
- 论文原文：PDF 作者块 / 脚注、TeX 的
\thanks{}/\email{}—— 最可信，直接采用。 - 作者机构主页：进入下面查到的 homepage，页面常公开
[email protected]。 - 交叉验证：与机构域名一致（如作者在 MIT 则邮箱多为
@mit.edu）才写入。
Crossref / OpenAlex / Semantic Scholar 一般不公开邮箱，别指望 API 直接给 email。
2. Homepage / 个人主页
- OpenAlex（免费无 key，最稳的作者定位）：
- 找论文作者：
https://api.openalex.org/works?filter=title.search:{TITLE}（或doi:{DOI}）， 取authorships[].author.id。 - 作者详情：
https://api.openalex.org/authors/{AUTHOR_ID}（稳定给orcid、last_known_institutions；homepage_url多为空，别指望它给主页）。 - 拿到机构后，去机构 / 实验室站点找作者个人页（个人页常直接列 email）。
- 找论文作者：
- Semantic Scholar Graph API（副源：无 key 易
429，命中再用）：- 论文：
https://api.semanticscholar.org/graph/v1/paper/search?query={TITLE}&fields=title,authors,externalIds。 - 作者：
https://api.semanticscholar.org/graph/v1/author/{AUTHOR_ID}?fields=name,url,homepage,affiliations,externalIds。
- 论文：
- ORCID（拿到 orcid 可交叉验证身份，取法见下方 ORCID 小节）。
- DBLP（学者主页常在
url字段）：https://dblp.org/search/author/api?q={NAME}&format=json。
- Google Scholar profile：搜索
{NAME} {机构/方向}，取https://scholar.google.com/citations?user=...。
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 · 197 lines · 100 tokens per session scan A bd071d36cff6
author-lookup is a skill published in the GitHub repository poco-ai/Agentero (446 stars, last pushed today), licensed MIT. It adds 100 tokens to every session and 3,846 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
channel_message
Use this skill to proactively send a one-way message to a user/session/channel, usually only when the user explicitly asks to send to a channel/session or when proactive notification is needed. First query sessions with qwenpaw chats list, then push with qwenpaw channels send.
tmux
Remote-control tmux sessions for interactive CLIs by sending keystrokes, capturing pane output, and managing terminal multiplexer windows. Enables parallel coding-agent orchestration, background process management, and REPL interaction via sockets. Use when the agent needs to launch, monitor, or coordinate…
things-mac
Manage Things 3 via the things CLI on macOS (add/update projects+todos via URL scheme; read/search/list from the local Things database). Use when a user asks Otto to add a task to Things, list inbox/today/upcoming, search tasks, or inspect projects/areas/tags.
apple-reminders
Manage Apple Reminders via the remindctl CLI on macOS (list, add, edit, complete, delete). Supports lists, date filters, and JSON/plain output. Use when the user asks about reminders, todos, tasks, to-do lists, "remind me", scheduling tasks, checking what is due today, completing or deleting reminders, or managing…
obsidian
Work with Obsidian vaults (plain Markdown notes) and automate via obsidian-cli. Use when the user asks about notes, vault management, PKM, knowledge base organization, wikilinks, or personal knowledge management in Obsidian.
computer-use
Read and drive native desktop applications through the accessibility layer — list on-screen apps, snapshot one window as a numbered element tree, then click / type / set a value / scroll / drag / run a named action, by element index or by screen coordinates. Use for work in a desktop app rather than a web page. Full…