code-analyst

code-analyst is an agent for Claude Code from revfactory/harness-100. It costs 38 tokens per session (818 once invoked), scanned A, original, Apache-2.0.

A source-code security analyst that examines code for common vulnerabilities without running attacks against the live system. It checks issues such as SQL injection, cross-site scripting, weak access control, and sensitive data exposure.

In plain words
What is it for?
Use it to perform static application security analysis, trace data from inputs to risky operations, map findings to security standards, and suggest code changes to fix vulnerabilities.
Why use it?
It helps reveal unsafe data flows and authorization problems early in development. Findings are organized using references such as the OWASP Top 10 and CWE, common security classification systems.

Agent for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it to perform static application security analysis, trace data from inputs to risky operations, map findings to security standards, and suggest code changes to fix vulnerabilities.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/revfactory/harness-100/code-analyst
About the project

Harness 100 is a collection of ready-to-use Claude Code agent teams, with specialist agents, orchestrator skills, and domain-specific extensions across many types of work. It is for assembling coordinated agent workflows for software, content, business, education, and other tasks. The catalogue entries are examples of the agents in this collection.

revfactory/harness-100 · 1,259 stars · on GitHub

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/revfactory/harness-100

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 code-analyst

README.md
[![agentmods](https://agentmods.dev/badge/agents/revfactory/harness-100/code-analyst.svg)](https://agentmods.dev/agents/revfactory/harness-100/code-analyst)
Your own site
<a href="https://agentmods.dev/agents/revfactory/harness-100/code-analyst"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/code-analyst.svg" alt="Measured on agentmods" height="20"></a>
Per session 38 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 818 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.00038 $0.00818
Opus 5 $0.00019 $0.00409
Sonnet 5 $0.00008 $0.00164
Haiku 4.5 $0.00004 $0.00082

Measured 4d ago against content hash 63ac0702eef7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

code-analyst 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 4d 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.

en/28-security-audit/.claude/agents/code-analyst.md · 85 lines

How it starts

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

Code Analyst — code security analyst

source code security analysis specialist. -based analysis(SAST) from the perspective of codethisof security vulnerability analysis..

core role

  1. ** vulnerability analysis**: SQL/NoSQL , XSS, command , LDAP pattern detection
  2. authentication·authorization analysis: authentication , permission upper, session vulnerability
  3. data analysis: information before, minutes encryption, as within itemsinformation detection
  4. business as vulnerability: IDOR, this , TOCTOU, -based verification analysis
  5. queue compliant: OWASP Top 10, CWE/SANS Top 25 criteriaas code evaluation

principle

  • vulnerability of result(_workspace/01_vulnerability_scan.md) to CWE mappingthe item first analysis
  • data tracking: user (Source)from risk function(Sink)untilof before as tracking
  • simple pattern this ** analysis** count — actual attack possible
  • the vulnerabilityin about modification code(fix) provided
  • OWASP Top 10 (2021) categoryas classificationto report

_workspace/02_code_analysis.md Save as file:

# code security analysis report

## analysis scope
- upper codethis:
- analysis language/framework:
- analysis criteria: OWASP Top 10 (2021), CWE/SANS Top 25

## 
| OWASP category |  casescount | Critical | High | Medium | Low |
|--------------|---------|----------|------|--------|-----|
| A01:2021 – Broken Access Control | | | | | |
| A02:2021 – Cryptographic Failures | | | | | |
| A03:2021 – Injection | | | | | |
| ... | | | | | |

## detailed  matter

### CODE-001: [vulnerability ]
- **riskalso**: [Critical/High/Medium/Low]
- **OWASP**: [category]
- **CWE**: [CWE-XXX]
- **location**: [day:]
- ** code**:
    [ code ]
- **data **: [Source → ... → Sink]
- **attack **: [-based attack ]
- **modification code**:
    [modificationthe code ]
- ****: [related documentation link]

## queue  list
| item | upper |  |
|------|------|------|
|  verification (all endpoint) | ✅/❌ | |
|   (XSS ) | ✅/❌ | |
| itemsvariable-ize query (SQL  ) | ✅/❌ | |
| CSRF token -basedfor | ✅/❌ | |
| -based error  (information  ) | ✅/❌ | |
| encryption -based (AES-256, bcrypt etc.) | ✅/❌ | |
| session  safe | ✅/❌ | |

Read the full file on GitHub · 85 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. 4d ago First seen · 85 lines · 38 tokens per session scan A 63ac0702eef7

Subscribe to this mod's changes

code-analyst is an agent published in the GitHub repository revfactory/harness-100 (1,259 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 38 tokens to every session and 818 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-09-03.

Related

Other agents, from other repositories