aid-report

aid-report is a skill for Claude Code from AndreVianna/aid-methodology. It costs 143 tokens per session (1,763 once invoked), scanned A, original, MIT.

A data-analysis tool that examines datasets, logs, usage metrics, or A/B test results and produces a checked report of what the data shows.

In plain words
What is it for?
Use it for exploratory analysis, metric investigation, usage analysis, and A/B test reports.
Why use it?
It turns raw measurements into conclusions while keeping negative results and data-quality limits visible.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions subagents; installed under .agents/ (shared by several agents).

Good fit Use it for exploratory analysis, metric investigation, usage analysis, and A/B test reports.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/andrevianna/aid-methodology/aid-report
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 AndreVianna/aid-methodology --skill aid-report
Clone the repo
git clone --depth 1 https://github.com/AndreVianna/aid-methodology

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 aid-report

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/andrevianna/aid-methodology/aid-report"><img src="https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 143 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,763 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.00143 $0.01763
Opus 5.5 $0.00057 $0.00705
Sonnet 5.5 $0.00029 $0.00353
Haiku 4.5 $0.00014 $0.00176

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

Security

Grade A, and why

aid-report 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 26d 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.

.agents/skills/aid-report/SKILL.md · 149 lines

How it starts

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

Report (analyze now, resolve nothing)

/aid-report analyzes data/usage now and returns a curated, verified insight report. Like /aid-research it resolves nothing -- it presents the picture and you decide -- but its subject is data (a dataset, logs, telemetry, metrics, an A/B result) rather than an open question.

  • Boundary: aid-report = a one-time analysis + insight. A durable, refreshable BI view is /aid-create-dashboard, not this. If the user wants the analysis to recur, that's a printed handoff to /aid-create-dashboard.
  • Not a numbered pipeline phase; does not route to /aid-execute.

State machine: INTAKE -> ANALYZE -> VERIFY (loop) -> PRESENT [user resolves] -> HANDOFF? -> DONE. Print the [State: NAME] -- {purpose} entry line on each state.


State: INTAKE

  1. Require a subject. Empty argument -> ask one bootstrapping question ("What data should I analyze, and what question about it?") and wait.
  2. Pick the path: Fast -- a clear data source + a clear analytical ask ("analyze the A/B results in results.csv", "error-rate breakdown from these logs") -> analyze now. Guided -- vague ("analyze our usage") -> scope which data, which metrics, what question first, then analyze.
  3. Classify complexity (model + effort): simple (small dataset, one metric) -> aid-researcher at sonnet / medium; standard/complex (large data, A/B significance, deep telemetry) -> opus / high. Verifier tier >= producer tier.
  4. Consult the Work Initiation Gate, then allocate the work folder + STATE. First run the gate (.aid/runtime/templates/work-initiation-gate.md): bash .aid/runtime/scripts/works/enumerate-works.sh (main tree + every git worktree). Empty -> allocate, no prompt. Works exist -> ask new-vs-continuation; on continuation route to the chosen work's resume door and STOP (allocate nothing); on new work: create and enter the worktree per the gate's § 3a step 2 (worktree-lifecycle.sh create <work-id> <name>, STOP on a non-zero exit or empty path, else enter the resolved path), then allocate (pipeline.path: lite, initiator: aid-report, lifecycle: Running, active_skill: aid-report; phase not driven), same as the other collapse skills.

Read the full file on GitHub · 149 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. 26d ago Changed 63e6111b21c2
  2. 2mo ago First seen · 149 lines · 143 tokens per session scan A 23a35c6138fe

Subscribe to this mod's changes

aid-report is a skill published in the GitHub repository AndreVianna/aid-methodology (6 stars, last pushed 11d ago), licensed MIT. It adds 143 tokens to every session and 1,763 once invoked, about $0.0006 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-09-03.

Related

aid-report compared with skills from other repositories

aid-report next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
aid-reportAndreVianna/aid-methodologySkill611d agoMITA143Claude Code
imagegenopenai/codexSkill134ktodayApache-2.0A113Codex
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79kyesterdayMITA200Claude Code, Codex
playwright-climicrosoft/playwrightSkill100kyesterdayApache-2.0A19Claude Code
browser-automationopenclaw/openclawSkill394ktodayMITA36Claude Code
systematic-debuggingobra/superpowersSkill314k4d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143ktodayMITA95Claude Code