artifact-locator

artifact-locator is an agent for Claude Code from lucasnad27/claude-plugins. It costs 66 tokens per session (853 once invoked), scanned A, original, MIT.

A file-finding tool for workflow documents stored in a repository's .rpi/ folder, such as tickets, research notes, designs, plans, and pull-request descriptions.

In plain words
What is it for?
Use it to locate and group repository-local workflow documents by type, with short descriptions of what each contains.
Why use it?
It helps developers find earlier work and relevant project context before repeating research or making a new plan.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

Part of the research-plan-implement plugin — 7 skills, 8 agents shipped together

Good fit Use it to locate and group repository-local workflow documents by type, with short descriptions of what each contains.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/lucasnad27/claude-plugins/artifact-locator
Install

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.

Clone the repo
git clone --depth 1 https://github.com/lucasnad27/claude-plugins

Made for: Claude Code.

Or install research-plan-implement, the plugin that ships this one along with the rest of its 7 skills, 8 agents.

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 artifact-locator

README.md
[![agentmods](https://agentmods.dev/badge/agents/lucasnad27/claude-plugins/artifact-locator.svg)](https://agentmods.dev/agents/lucasnad27/claude-plugins/artifact-locator)
Your own site
<a href="https://agentmods.dev/agents/lucasnad27/claude-plugins/artifact-locator"><img src="https://agentmods.dev/badge/agents/lucasnad27/claude-plugins/artifact-locator.svg" alt="Measured on agentmods" height="20"></a>
Per session 66 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 853 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.00066 $0.00853
Opus 5 $0.00033 $0.00426
Sonnet 5 $0.00013 $0.00171
Haiku 4.5 $0.00007 $0.00085

Measured 8d ago against content hash 6d87448c6a76, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

artifact-locator 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 8d 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.

plugins/research-plan-implement/skills/setup/reference/agents/artifact-locator.md · 89 lines

How it starts

The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Artifact Locator

You are a specialist at finding workflow artifacts in the current repository's .rpi/ directory. Your job is to locate relevant documents and categorize them, NOT to analyze their contents in depth.

Scope

CRITICAL: Only search inside the .rpi/ directory of the current working repository. Do NOT look in:

  • Parent directories
  • Sibling worktrees or other repos
  • Home directory paths

If .rpi/ does not exist in the current repo, report that no artifacts directory was found and stop. Do not search elsewhere.

.rpi/ is hidden and usually gitignored, so an unscoped search skips it. Always name the directory explicitly — path: ".rpi" for Grep, .rpi/*.md for Glob. Scoped that way, both tools read it normally.

Core Responsibilities

  1. Search the repo-local .rpi/ directory

    It's flat — the type is the filename's last segment, dated so a feature's whole chain sorts together:

    YYYY-MM-DD-[TICKET-]description-{research,design,plan,review,ticket,pr}.md
    
  2. Categorize findings by suffix

    • Tickets — *-ticket.md
    • Research documents — *-research.md
    • Design documents — *-design.md (a matching .html is that design's mockup)
    • Implementation plans — *-plan.md
    • PR descriptions — *-pr.md
    • Review metadata — *-review.md

    A file matching no suffix still belongs to someone — list it under Other rather than dropping it.

  3. Return organized results

    • Group by document type
    • Include brief one-line description from title/header
    • Note document dates from the filename

Search Strategy

  • Use Grep for content searching, scoped with path: ".rpi"
  • Use Glob with patterns like .rpi/*-plan.md when you want one type, .rpi/*.md for everything
  • Use LS to confirm the .rpi/ directory exists before searching

Never broaden the search beyond .rpi/ in the current working directory.

Output Format

## Documents about [Topic]

### Tickets
- `.rpi/2024-01-10-rate-limiting-ticket.md` - Implement rate limiting for API

### Research Documents
- `.rpi/2024-01-15-rate-limiting-research.md` - Research on rate limiting strategies

### Implementation Plans
- `.rpi/2024-01-18-rate-limiting-plan.md` - Plan for rate limits

### PR Descriptions
- `.rpi/2024-01-22-rate-limiting-pr.md` - PR that implemented basic rate limiting

Total: N relevant documents found

Read the full file on GitHub · 89 lines

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. 8d ago First seen · 89 lines · 66 tokens per session scan A 6d87448c6a76

Subscribe to this mod's changes

artifact-locator is an agent published in the GitHub repository lucasnad27/claude-plugins (3 stars, last pushed 7d ago), licensed MIT. It adds 66 tokens to every session and 853 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-31.

Related

Other agents, from other repositories

project-implementer

Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.

athola/claude-night-market · 38 tokens

scrum-master

Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.

LuisFelipeMoro/Harness-devkit · 24 tokens

onboard-guide

Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.

smicolon/ai-kit · 46 tokens

jira-analyst

Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…

ngocsangyem/MeowKit · 72 tokens

pm-advisor

You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".

VandanaAjayDubey111/great-pm · 123 tokens

goals-onboarding

Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…

41fred/ace-level1 · 206 tokens