SKILLEMALL.ai

CF Agent Cost Report

Believable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json.

thedotmack/claude-mem Agent Skills author: thedotmack Apache-2.0 49 files · 39 scripts body ≈ 5 044 tokens Open the sourcegithub.com↗ analyzed 6 d ago

Believable agent cost report for any period, default the last 7 full days PT, not counting today.

As a process F 34/100 · No process to follow — References files that are not bundled: scripts/**

AnalyzerGitHubData and analyticsAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
C
83/100
safety, quality, tests
Safety 60%
95
Quality 40%
66
Run on models
none yet
Process rating
F
34/100
No process to follow
References files that are not bundled: scripts/**
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: Agent Cost Report (thedotmack/claude-mem)

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Broad scope medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

How to improve

  1. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
  2. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 1

✓ No critical or high findings

Medium and low: 1
  • medium Broad scope meta-broad-allowed-tools SKILL.md:1
    Broad tool permissions pre-approved: Bash
    allowed-tools: Bash Read Write AskUserQuestion mcp__plugin_claude-mem_mcp-search__search mcp__plugin_claude-mem_mcp-search__timeline mcp__plugin_claude-mem_mcp-search__get_observations

Files scanned: 48. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • warning body-long SKILL.md body ≈ 5044 tokens (recommended < 5000); move details to references/
  • warning missing-ref reference to a missing file: scripts/**

Process rating: all ten parameters 34/100

Will not run. References files that are not bundled: scripts/**
  • 0Tools and files. 1 referenced file(s) missing: scripts/**
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 40Consistency. Frontmatter name (Agent Cost Report) differs from the folder (agent-cost-report)
  • 50Failures and branches. 0 branches, has a failure section
  • 70Execution cost. Instruction body is 5044 tokens
  • 100Steps. 64 steps
  • 100Running it twice. Mutating operations check current state
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 19 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (6 tags): a typed call is more reliable

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +3Description length 342: enough signal without eating the budget
  • +4Structure: 21 headings
  • +3Step-by-step instructions: 64 items
  • +4Has examples (1 code blocks)
  • +3All 1 scripts are documented

Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.