teamctl: Agent for Claude Code

.claude/agents/prior-art-checker.md

prior-art-checker is an agent for Claude Code from Alireza29675/teamctl. It costs 73 tokens per session (495 once invoked), scanned A, original, MIT.

A read-only checker looks for an idea in GitHub issues, pull requests, the codebase, and established projects or products elsewhere.

In plain words
What is it for?
Use it before filing a teamctl issue or asking whether a feature exists. It reports duplicates, related work, or genuinely new ideas, including matching issue numbers and code or documentation paths.
Why use it?
It helps prevent duplicate work and replaces guesses about whether something has already been built with evidence about matches and differences.

Agent for Claude Code

Written for Claude Code: background in frontmatter. Also seen: model in frontmatter.

This is Alireza29675/teamctl's own configuration. It tells Claude Code how to work on teamctl itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything teamctl configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/Alireza29675/teamctl/main/.claude/agents/prior-art-checker.md
Clone the repo
git clone --depth 1 https://github.com/Alireza29675/teamctl

Made for: Claude Code.

Wrote 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.

agentmods badge for prior-art-checker

README.md
[![agentmods](https://agentmods.dev/badge/agents/alireza29675/teamctl/prior-art-checker/github.svg)](https://agentmods.dev/agents/alireza29675/teamctl/prior-art-checker)
Your own site
<a href="https://agentmods.dev/agents/alireza29675/teamctl/prior-art-checker"><img src="https://agentmods.dev/badge/agents/alireza29675/teamctl/prior-art-checker/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.

agentmods 80×15 button for prior-art-checker

Your own site · 80×15
<a href="https://agentmods.dev/agents/alireza29675/teamctl/prior-art-checker"><img src="https://agentmods.dev/badge/agents/alireza29675/teamctl/prior-art-checker.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 73 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 495 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00073 $0.00495
Opus 5 $0.00036 $0.00247
Sonnet 5 $0.00015 $0.00099
Haiku 4.5 $0.00007 $0.00049

Measured 10d ago against content hash 365de6d72e05, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

prior-art-checker 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 10d 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.

.claude/agents/prior-art-checker.md · 26 lines

What it actually says

You are a prior-art checker working for Sage, the co-thinker on the team that builds teamctl. You're spawned with an idea or proposed feature. Your job is to find out whether it already exists — in the issue tracker, in the codebase, or in the wider world — before anyone spends effort on it.

Ground yourself first, every run: re-read the idea as given, then go to source. Don't answer from memory.

Do this:

  • Search open and closed GitHub issues for duplicates: gh issue list --state all --search "<terms>", then gh issue view <n> on the close matches. Also check PRs (gh pr list --state all --search).
  • Grep and glob the repo (crates/, docs/, examples/, .team/) for anything already built toward this — a flag, a schema field, a render path, a docs page.
  • Search the web for established products, OSS projects, and common approaches to the same problem.

Return, in this shape:

  1. Exists? — yes (duplicate) / partial (related work) / no (genuinely new).
  2. In-repo / in-tracker — matching issues (number + title + state) and code/docs paths, or "none found".
  3. Prior art — external products/projects solving this, each with a link, or "none notable".
  4. How it differs — if related work exists, the honest gap between it and the idea.
  5. Recommendation — file fresh / extend issue #N / drop as duplicate / needs sharpening.

Stay in your lane: you search and report, you never open issues or edit files. Read before asserting — cite the issue number, file path, or URL behind every claim. If nothing matches, say "no prior art found" plainly rather than padding.

Changes

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.

  1. 10d ago First seen · 26 lines · 73 tokens per session scan A 365de6d72e05

Subscribe to this mod's changes

prior-art-checker is an agent published in the GitHub repository Alireza29675/teamctl (20 stars, last pushed 1mo ago), licensed MIT. It adds 73 tokens to every session and 495 once invoked, about $0.0004 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.

Related

Other agents, from other repositories

claude-deep-review

Internal Claude subagent for deep code review — security vulnerabilities, bug detection, and performance analysis. Has native codebase access (Read, Grep, Glob, Bash) to trace input paths, follow call chains, profile hot paths, and verify assumptions. Launched automatically by council review workflows — not invoked…

rube-de/cc-skills · 71 tokens

deep-reviewer

Deep review agent for CI: unconstrained code review that traces control flow across function and file boundaries, follows call sites, and catches cross-cutting bugs that specialist agents miss.

rube-de/cc-skills · 39 tokens

test-analyzer

Test coverage agent for CI: reviews PR diffs for missing test coverage, untested edge cases, inadequate error path testing, and test quality issues. Focuses on behavioral coverage over line metrics.

rube-de/cc-skills · 43 tokens

guidelines-checker

Guidelines compliance agent for CI: checks CLAUDE.md rules, style conventions, naming patterns, architectural consistency, and coding standards compliance in PR diffs.

rube-de/cc-skills · 37 tokens

team_lead_agent

A team-coordination agent for running a complete research project from defining the question through literature review, coding, experiments, iteration, paper writing, and delivery.

BingHanOfUESTC/open_agent_team · 53 tokens

critic_agent

A critical-review agent for short stories that scores the draft’s opening, characters, structure, scenes, language, emotional effect, and originality. It gives specific revision instructions and decides whether the draft passes.

BingHanOfUESTC/open_agent_team · 68 tokens