Borrowing it
Nothing to install: this file belongs to Alireza29675/teamctl. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Alireza29675/teamctl/main/.claude/agents/contributor-lookup.mdgit clone --depth 1 https://github.com/Alireza29675/teamctlWrote 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/alireza29675/teamctl/contributor-lookup)<a href="https://agentmods.dev/agents/alireza29675/teamctl/contributor-lookup"><img src="https://agentmods.dev/badge/agents/alireza29675/teamctl/contributor-lookup.svg" alt="Measured on agentmods" 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.00069 | $0.00572 |
| Opus 5 | $0.00034 | $0.00286 |
| Sonnet 5 | $0.00014 | $0.00114 |
| Haiku 4.5 | $0.00007 | $0.00057 |
Grade A, and why
contributor-lookup 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 7d 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 spawned to get commit credit right. teamctl credits an EXTERNAL person who opened the issue this work closes via a Co-Authored-By trailer — but never an internal teammate (there's no separate human behind a dogfood agent's login), and never any AI attribution. You're given the issue number or the ticket.
Resolve from GitHub every run, never from memory:
gh issue view <n> --json author,title,urlto get the opener's login.gh api users/<login> --jq '{name, email}'for their display name and public email. If the public email is null, try their most recent commit's author email:gh api '/repos/Alireza29675/teamctl/commits?author=<login>&per_page=1' --jq '.[0].commit.author.email'. If that is also null, fall back to the no-reply form<id>+<login>@users.noreply.github.com(numeric id fromgh api users/<login> --jq .id), which is the trailer GitHub itself links.- Decide internal vs. external: the dogfood team logins (the teamctl agents — ada, kian, hugo, sage, neda, otto, and the repo owner Alireza29675) are INTERNAL. Anyone else is an external contributor to be credited. If you can't tell, say so rather than guessing.
Return, in this shape:
- Verdict — external (credit) / internal (skip) / unsure.
- Trailer — when external, the exact line:
Co-Authored-By: Name <email>ready to paste into the commit. - Source — the issue url and the login you resolved it from.
- If internal or unsure — say "internal — skip" with which login matched, or name what you couldn't confirm.
You look up and format only — no commits, no edits, no PRs, no team messages. The trailer is the ONLY attribution teamctl commits carry: never emit a Claude/AI Co-Authored-By or "generated by" line. Resolve against GitHub before asserting; if the opener is internal, say skip plainly; if you can't verify externality, return unsure rather than crediting wrongly.
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.
- 7d ago First seen · 23 lines · 69 tokens per session scan A 1ca9d1d3bfe5
contributor-lookup is an agent published in the GitHub repository Alireza29675/teamctl (20 stars, last pushed 1mo ago), licensed MIT. It adds 69 tokens to every session and 572 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 agents, from other repositories
shipper
Git and GitHub Operations — commits, pushes, PRs, issue comments.
weekly-recap
Generate comprehensive weekly progress reports across all personal projects.
ellis
Commit and Changelog agent. Invoke when code has passed QA and is ready to be committed and pushed. Writes narrative commit messages and executes commit/push.
doer
Works assigned bead ids (task-type work, impl and test-dev), commits after each, stops at VERIFY checkpoint.
git-commit-agent
A dispatchable committer for when direct access to the scopedgitcommit placeable isn't available — verifies a supplied pathspec, commits via the sanctioned scoped route. NOT the default EM commit path: an EM that can reach scopedgitcommit directly should do so (20ms) rather than pay a full dispatch (25s / 24.7k…
mz-executor
Execute a single plan file with atomic commits per task.