agentleFS
Sign inStart free
zedarvateszedarvates/botte-secrete/skills/metrics/SKILL.md

metrics

Skill2 starsChanged 3 months agoMITView on GitHub

Cost-focused project metrics, broken down per component — LOC by language and component, duplicate-function groups, directive health, always-on context cost (CLAUDE.md tokens × turns), local-routing posture, skill-search tokens avoided, and the audit's own (near-zero) cost. Use when the user wants to quantify a project's token/cost profile, see LOC/health per component, or measure what the toolkit saves.

20 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use knowledge-graph, scan and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ddehartSkill

    knowledge-graph

    Search, capture, and query the claude-code-plugins knowledge graph. Use when asked to "capture this", "add this to the graph", "what do we know about X", "update the graph", "check the graph for X", or when a decision, pattern, or non-obvious fact surfaces mid-session that's worth recording. Also: "log an observation", "what patterns do we have about skill triggering", "any decisions on the knowledge-commons plugin", "what do we know about the commit-creator agent".

    Also in 3 projects that use this

  • rajnavakotiSkill

    scan

    Run the AI dashboard scanner and generate the HTML report.

    Also in 3 projects that use this

  • MicrosoftSkill

    retrospective

    Review how work went and improve the next round. USE WHEN asked for a retro, delays, or process lessons. DO NOT USE for code review or transcript replay.

    Also in 3 projects that use this

  • OpenAISkill

    observability

    Vercel Observability expert guidance — Drains (logs, traces, speed insights, web analytics), Web Analytics, Speed Insights, runtime logs, custom events, OpenTelemetry integration, and monitoring dashboards. Use when instrumenting, debugging, or optimizing application performance and user experience on Vercel.

    Also in 3 projects that use this

  • BlockSkill

    plan

    Draft a TDD, PRD, or lightweight plan in the conversation without committing it.

    Also in 5 projects that use this

  • 0xSeroSkill

    security

    Also in 3 projects that use this

The file

Create a free account to mount
Files
SKILL.md

metrics — quantify a project's token/cost profile

Surfaces the numbers an audit should give you, framed around cost. A multi-stack project (website + game server + client + tools) has no single number, so everything is broken down per component.

python -m skills.metrics.cli <project>
python -m skills.metrics.cli <project> --porthos reports/<proj>/audit-report.json --json

What it reports

  • LOC by language and by top-level component (with bars).
  • Duplicate-function groups (stdlib AST, free).
  • Directive health + always-on context cost: instruction tokens × turns — e.g. a 2.3k-token CLAUDE.md ≈ 70k tokens/session just re-sending rules.
  • Local-routing posture: backends present → cheap work at 0 cloud tokens.
  • Skill-search tokens avoided by find_skills (catalog × ~150 tok).
  • The audit's own cost: analysis_llm_tokens = 0 — the scans are deterministic Python; only synthesis by the orchestrating model costs tokens.
  • Deep audit summary (health / dead code / secrets) if a Porthos audit-report.json is reachable (.botte/ or --porthos).

Why this framing

The headline an audit should produce: "analysis cost 0 tokens; your always-on instructions cost ~70k/session; local routing can move cheap work to 0 cloud tokens." That's the number that justifies the toolkit.

Exposed via [[llm_mcp]] as the metrics tool. Related: [[infra_advisor]] (auto audit), [[directives_audit]], [[skill_finder]], [[bootstrap]].

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free