pillar-analyzer

pillar-analyzer is an agent for Claude Code from agent-next/agent-ready. It costs 14 tokens per session (793 once invoked), scanned A, original, MIT.

An agent that examines one area of a software project’s readiness for coding-agent work. It checks areas such as documentation, testing, security, builds, environment setup, and agent configuration.

In plain words
What is it for?
Use it to analyze a selected readiness area, such as tests or documentation, from a project path and receive passed checks, findings, a level, and prioritized improvements.
Why use it?
It turns a broad readiness review into evidence-based findings, scores, and recommendations for one area at a time.

Agent for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter; reads .claude/ paths; mentions AGENTS.md.

Good fit Use it to analyze a selected readiness area, such as tests or documentation, from a project path and receive passed checks, findings, a level, and prioritized improvements.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/agent-next/agent-ready/pillar-analyzer
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/agent-next/agent-ready

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 pillar-analyzer

README.md
[![agentmods](https://agentmods.dev/badge/agents/agent-next/agent-ready/pillar-analyzer/github.svg)](https://agentmods.dev/agents/agent-next/agent-ready/pillar-analyzer)
Your own site
<a href="https://agentmods.dev/agents/agent-next/agent-ready/pillar-analyzer"><img src="https://agentmods.dev/badge/agents/agent-next/agent-ready/pillar-analyzer/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 pillar-analyzer

Your own site · 80×15
<a href="https://agentmods.dev/agents/agent-next/agent-ready/pillar-analyzer"><img src="https://agentmods.dev/badge/agents/agent-next/agent-ready/pillar-analyzer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 793 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.00014 $0.00793
Opus 5.5 $0.00006 $0.00317
Sonnet 5.5 $0.00003 $0.00159
Haiku 4.5 $0.00001 $0.00079

Measured 1mo ago against content hash b55e7f5faf41, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

pillar-analyzer 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 1mo 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.

packages/plugin/agents/pillar-analyzer.md · 116 lines

How it starts

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

Pillar Analyzer Agent

Specialized agent for deep analysis of a single pillar. Can be invoked in parallel for all 10 pillars.

Input

  • pillar: The pillar to analyze (docs, style, build, test, security, observability, env, task_discovery, product, agent_config)
  • path: Project root path

Output

Returns a structured analysis:

{
  "pillar": "agent_config",
  "score": 55,
  "level": "L2",
  "findings": [
    { "check": "AGENTS.md exists", "passed": true, "evidence": "AGENTS.md found" },
    { "check": "MCP configured", "passed": false, "evidence": "No mcp.json found" }
  ],
  "recommendations": [
    { "priority": "high", "action": "Configure MCP server", "impact": "+15" }
  ]
}

Pillar-Specific Analysis

docs

Read: README.md, AGENTS.md, CONTRIBUTING.md, docs/ Evaluate: Clarity, completeness, accuracy, AI-friendliness

style

Read: .eslintrc*, .prettierrc*, tsconfig.json, .pre-commit-config.yaml Evaluate: Rule consistency, TypeScript strictness, enforcement

build

Read: package.json, .github/workflows/*.yml, Makefile Evaluate: Build scripts work, CI configured, caching enabled

test

Read: test/, jest.config.*, coverage/ Evaluate: Test existence, coverage percentage, integration tests

security

Read: .gitignore, .github/dependabot.yml, CODEOWNERS Evaluate: Secret coverage, dependency updates, ownership

observability

Read: package.json (logging deps), tracing config Evaluate: Structured logging, tracing, metrics

env

Read: .env.example, .devcontainer/, docker-compose.yml Evaluate: Env documentation, local setup, containerization

task_discovery

Read: .github/ISSUE_TEMPLATE/, .github/PULL_REQUEST_TEMPLATE.md Evaluate: Template quality, required fields, automation

product

Read: package.json (feature flag/analytics deps) Evaluate: Feature flags, analytics, experimentation

agent_config (NEW)

Read: AGENTS.md, .claude/, .cursorrules, mcp.json Evaluate: Agent instructions, permissions, MCP integration, hooks

Read the full file on GitHub · 116 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. 1mo ago First seen · 116 lines · 14 tokens per session scan A b55e7f5faf41

Subscribe to this mod's changes

pillar-analyzer is an agent published in the GitHub repository agent-next/agent-ready (33 stars, last pushed today), licensed MIT. It adds 14 tokens to every session and 793 once invoked, about $0.0001 per session on Opus 5.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.