analyze

analyze is a skill for Claude Code, Codex from tinh2/skills-hub-registry. It costs 66 tokens per session (3,447 once invoked), scanned A, original, no licence file.

A codebase audit that follows a feature across its user interface, application logic, and database. It checks whether the parts agree, identifies missing connections and security gaps, and can automatically fix critical and warning issues.

In plain words
What is it for?
Use it after building features, before a release, or when behaviour seems inconsistent across the application.
Why use it?
It helps uncover features that look complete but fail because a handler is missing, data does not match, or one layer is not connected to another.

Skill for Claude CodeCodex

Which agent this was written for is unclear — body not stored (licence); the path alone says nothing.

Good fit Use it after building features, before a release, or when behaviour seems inconsistent across the application.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tinh2/skills-hub-registry/analyze
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.

Any agent
npx skills add tinh2/skills-hub-registry --skill analyze
Clone the repo
git clone --depth 1 https://github.com/tinh2/skills-hub-registry

Made for: Claude Code, Codex.

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 analyze

README.md
[![agentmods](https://agentmods.dev/badge/skills/tinh2/skills-hub-registry/analyze/github.svg)](https://agentmods.dev/skills/tinh2/skills-hub-registry/analyze)
Your own site
<a href="https://agentmods.dev/skills/tinh2/skills-hub-registry/analyze"><img src="https://agentmods.dev/badge/skills/tinh2/skills-hub-registry/analyze/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 analyze

Your own site · 80×15
<a href="https://agentmods.dev/skills/tinh2/skills-hub-registry/analyze"><img src="https://agentmods.dev/badge/skills/tinh2/skills-hub-registry/analyze.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 66 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,447 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 unknown 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.03447
Opus 5.5 $0.00026 $0.01379
Sonnet 5.5 $0.00013 $0.00689
Haiku 4.5 $0.00007 $0.00345

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

Security

Grade A, and why

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

analysis/analyze/SKILL.md · 357 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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 · 357 lines · 66 tokens per session scan A 8f3afd9a2c43

Subscribe to this mod's changes

analyze is a skill published in the GitHub repository tinh2/skills-hub-registry (22 stars, last pushed 1mo ago), with no licence file. It adds 66 tokens to every session and 3,447 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

Bug Root Cause Analyzer

Systematically diagnoses bugs by tracing execution flow and identifying root causes vs symptoms.

Notysoty/openagentskills · 20 tokens

log-diagnostic

A log-analysis tool that detects JSON, syslog, and Nginx formats and reports grouped errors, occurrence counts, severity levels, and time distribution. It can filter entries by level or time range and export JSON.

serejaris/kimi-skills · 88 tokens

log-analysis

A guide to reading and searching system and application logs. Logs are text records that describe what software and servers are doing.

chaterm/terminal-skills · 7 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

serejaris/kimi-skills · 71 tokens

spark-engineer

Use when writing Spark jobs, debugging performance issues, or configuring cluster settings for Apache Spark applications, distributed data processing pipelines, or big data workloads. Invoke to write DataFrame transformations, optimize Spark SQL queries, implement RDD pipelines, tune shuffle operations, configure…

Jeffallan/claude-skills · 75 tokens

debugging-wizard

Parses error messages, traces execution flow through stack traces, correlates log entries to identify failure points, and applies systematic hypothesis-driven methodology to isolate and resolve bugs. Use when investigating errors, analyzing stack traces, finding root causes of unexpected behavior, troubleshooting…

Jeffallan/claude-skills · 70 tokens