code-stats
Analyze Code Size and Semantic Diffs
Teams need quick visibility into codebase size, language mix, and meaningful changes. This skill guides Claude, Codex, and Claude Code to run tokei and difftastic safely.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "code-stats" from https://skillstore.io/skills/0xdarkmatter-code-stats.md and its manifest at https://skillstore.io/api/skills/0xdarkmatter-code-stats/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "code-stats". Summarize this repository with tokei.
Expected outcome:
- Shows a language breakdown with files, total lines, code lines, comments, and blanks.
- Highlights the largest languages and notes excluded folders.
Using "code-stats". Compare old.ts and new.ts with difftastic.
Expected outcome:
- Explains that formatting-only changes were ignored.
- Lists moved functions, renamed variables, and semantic edits that affect review.
Using "code-stats". Build a CI line-count report.
Expected outcome:
- Reports whether the current code count is under the configured limit.
- Provides a short trend summary suitable for a pull request comment.
Security Audit
SafeAll static findings were adjudicated as false positives. The flagged lines are documentation examples for local tokei and difftastic commands, git configuration, pager use, and jq filters; I found no prompt injection, network access, or data exfiltration intent.
Risk Factors
๐ Filesystem access (5)
โ๏ธ External commands (23)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/0xdarkmatter-code-stats/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/0xdarkmatter-code-stats?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/0xdarkmatter-code-stats?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/0xdarkmatter-code-stats/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/0xdarkmatter-code-stats.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
0xDarkMatter. (2026). code-stats security audit report (audit version 9) [Author version unspecified]. Skillstore. https://skillstore.io/skills/0xdarkmatter-code-stats/audits/9BibTeX citation
@techreport{0xdarkmatter-0xdarkmatter-code-stats-2026,
author = {0xDarkMatter},
title = {code-stats security audit report (audit version 9)},
institution = {Skillstore},
year = {2026},
number = {9},
url = {https://skillstore.io/skills/0xdarkmatter-code-stats/audits/9},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "code-stats security audit report (audit version 9)"
version: "unspecified"
type: report
authors:
- name: "0xDarkMatter"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/0xdarkmatter-code-stats/audits/9"
identifiers:
- type: other
value: "skillstore:0xdarkmatter-code-stats:audit:9"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Estimate project size
Get language totals before planning a migration or staffing review.
Review refactoring impact
Compare files or branches semantically to separate behavior changes from formatting noise.
Track repository growth
Create repeatable tokei reports for CI size checks and trend tracking.
Try These Prompts
Use tokei to summarize this repository by language. Exclude dependency and build folders. Explain total code, comments, and blanks.
Use difftastic to compare these two files semantically. Explain moved code, renamed symbols, and real behavior changes.
Run tokei with compact and machine-readable output. Summarize language totals and note directories that should be excluded next time.
Compare the current branch against main with difftastic. Focus on semantic changes and ignore formatting-only churn.
Best Practices
- Exclude dependency, generated, and build folders before sharing totals.
- Use semantic diffs for refactors where formatting changes obscure behavior.
- State the paths or branches to compare before asking for a report.
Avoid
- Do not run counts on private or unrelated folders without permission.
- Do not compare generated artifacts when reviewing source changes.
- Do not treat line counts as a direct measure of engineering value.
Frequently Asked Questions
Which tools does this skill use?
Does it install tools automatically?
Can it analyze hidden or ignored files?
Can it compare branches?
Does it send data over the network?
Is it useful for non-code files?
Developer Details
Author
0xDarkMatterLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
2e36836131679643f7a49e4cfff588d67adc404b
Maintenance freshness
7/18/2026
Usage
25 downloads ยท 173 views
File structure
๐ assets/
๐ .gitkeep
๐ references/
๐ difft-advanced.md
๐ tokei-advanced.md
๐ scripts/
๐ .gitkeep
๐ SKILL.md