development-workflows-research-agent

development-workflows-research-agent is an agent for Claude Code from shanraisshan/claude-code-best-practice. It costs 33 tokens per session (1,065 once invoked), scanned A, original, MIT.

A research workflow for analyzing Claude Code repositories, which are code projects containing instructions and tools for an AI coding assistant. It fetches repository details, counts agents, skills, and commands, and examines workflow projects.

In plain words
What is it for?
Use it to research GitHub projects, check their star counts, count their workflow components, inspect release information, and produce a structured findings report.
Why use it?
It organizes the checks needed to compare these repositories and records a confidence level for each finding.

Agent for Claude Code

About the project

claude-code-best-practice is a repository of agents, commands, skills, hooks, plugins, and configuration guidance for Claude Code. It helps developers organize repeatable workflows and apply agentic engineering practices, including in monorepos. The catalogue entries are its reusable Claude Code workflow components.

shanraisshan/claude-code-best-practice · 65,618 stars · on GitHub · linkedin.com

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.

agentmods
npx agentmods add agents/shanraisshan/claude-code-best-practice/development-workflows-research-agent
Clone the repo
git clone --depth 1 https://github.com/shanraisshan/claude-code-best-practice

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 development-workflows-research-agent

README.md
[![agentmods](https://agentmods.dev/badge/agents/shanraisshan/claude-code-best-practice/development-workflows-research-agent.svg)](https://agentmods.dev/agents/shanraisshan/claude-code-best-practice/development-workflows-research-agent)
Your own site
<a href="https://agentmods.dev/agents/shanraisshan/claude-code-best-practice/development-workflows-research-agent"><img src="https://agentmods.dev/badge/agents/shanraisshan/claude-code-best-practice/development-workflows-research-agent.svg" alt="Measured on agentmods" height="20"></a>
Per session 33 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,065 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00033 $0.01065
Opus 5 $0.00016 $0.00532
Sonnet 5 $0.00007 $0.00213
Haiku 4.5 $0.00003 $0.00106

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

Security

Grade A, and why

development-workflows-research-agent 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 6d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.claude/agents/development-workflows-research-agent.md · 127 lines

How it starts

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

Development Workflows Research Agent

You are a senior open-source analyst researching Claude Code workflow repositories. Your job is to fetch repo data, count artifacts, and return a structured findings report. Rate your confidence 0-1 on each data point. Be exhaustive — check every directory, every file listing, every release page. I'll tip you $200 for perfectly accurate counts. I bet you can't get every number right — prove me wrong.

This is a read-only research workflow. Fetch sources, analyze, and return findings. Do NOT modify any local files.


Research Protocol

For EACH repository you are asked to research, follow this exact protocol:

Step 1: Get Star Count

Fetch the GitHub API endpoint:

https://api.github.com/repos/{owner}/{repo}

Extract the stargazers_count field. Round to nearest k:

  • 98,234 → 98k
  • 1,623 → 1.6k
  • 847 → 847

If the API fails, fetch the repo's main page and extract stars from the HTML.

Step 2: Count Agents

Search for agent definitions in these locations (in order):

  1. agents/ directory at repo root
  2. .claude/agents/ directory
  3. References in README.md or AGENTS.md to agent names/roles

For each location found, use the GitHub API to list directory contents:

https://api.github.com/repos/{owner}/{repo}/contents/{path}

Count .md files that are agent definitions. Exclude README.md, INDEX.md, and non-agent files.

Also check for implicit agents — agents dispatched by skills or commands but not defined as separate files. Report these separately.

Step 3: Count Skills

Search for skill definitions in these locations:

  1. skills/ directory at repo root
  2. .claude/skills/ directory
  3. Subdirectories containing SKILL.md files

Count skill folders (each folder with a SKILL.md is one skill). Also check for community/external skill repos referenced in the README.

Step 4: Count Commands

Search for command definitions in these locations:

  1. commands/ directory at repo root
  2. .claude/commands/ directory
  3. Subdirectories within commands/

Read the full file on GitHub · 127 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. 6d ago First seen · 127 lines · 33 tokens per session scan A 78f37178ee3b

Subscribe to this mod's changes

development-workflows-research-agent is an agent published in the GitHub repository shanraisshan/claude-code-best-practice (65,618 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 1,065 once invoked, about $0.0002 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

security-reviewer

Use proactively when attacker-controlled input, trust boundaries, authorization decisions, sensitive sinks, secrets, or security-impacting changes require exploitability analysis. Do not use for generic correctness review without a meaningful security boundary.

zebbern/claude-code-guide · 45 tokens

cheatsheet-language-reviewer

Language and editorial reviewer for OWASP cheat sheet changes. Checks US English correctness, grammar, clarity for non-native readers, and the project's structural/style conventions. Invoked by /review-cheatsheet-pr.

OWASP/CheatSheetSeries · 48 tokens

integration-reviewer

Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.

FlorianBruniaux/claude-code-ultimate-guide · 57 tokens

migration-upgrade-prompt

Use this when: planning or executing a framework, runtime, database, or major-dependency migration, or a toolchain swap, without downtime. Skip to: Protocol · Phase 1: MAP · Codemods first · Phase 4: RISK-ASSESS · Remember.

Rtur2003/Claude-Code-Promts-Skills · 0 tokens

migration-specialist

Framework upgrades, codemod strategies, version migration planning, and legacy modernization specialist. Use when upgrading frameworks, migrating between technologies, or modernizing legacy codebases. Trigger phrases: migration, upgrade, framework migration, version upgrade, codemod, legacy, modernize, breaking…

travisjneuman/.claude · 67 tokens

architect

System architect responsible for component boundaries, integration points, data flow, ADRs, technology selection, and API contracts. Invoke for architecture decisions, dependency strategy, performance planning, and interface design. Read-only — produces decisions and documentation.

irahardianto/awesome-agv · 48 tokens