file-line-audit

file-line-audit is a skill for Claude Code from bosens-China/tc39-atlas. It costs 74 tokens per session (1,377 once invoked), scanned A, original, MIT.

A repository audit tool that finds source files at or above a chosen line-count limit while respecting ignore rules.

In plain words
What is it for?
Use it to scan selected source languages and directories, excluding ignored or generated files, and report only files over the threshold.
Why use it?
It shows where oversized files may be making a codebase harder to understand, test, or maintain.

Skill for Claude Code

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

Good fit Use it to scan selected source languages and directories, excluding ignored or generated files, and report only files over the threshold.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/bosens-china/tc39-atlas/file-line-audit
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 bosens-China/tc39-atlas --skill file-line-audit
Clone the repo
git clone --depth 1 https://github.com/bosens-China/tc39-atlas

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 file-line-audit

README.md
[![agentmods](https://agentmods.dev/badge/skills/bosens-china/tc39-atlas/file-line-audit/github.svg)](https://agentmods.dev/skills/bosens-china/tc39-atlas/file-line-audit)
Your own site
<a href="https://agentmods.dev/skills/bosens-china/tc39-atlas/file-line-audit"><img src="https://agentmods.dev/badge/skills/bosens-china/tc39-atlas/file-line-audit/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 file-line-audit

Your own site · 80×15
<a href="https://agentmods.dev/skills/bosens-china/tc39-atlas/file-line-audit"><img src="https://agentmods.dev/badge/skills/bosens-china/tc39-atlas/file-line-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 74 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,377 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.00074 $0.01377
Opus 5 $0.00037 $0.00688
Sonnet 5 $0.00015 $0.00275
Haiku 4.5 $0.00007 $0.00138

Measured 12d ago against content hash 11811fbc14a7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

file-line-audit 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 12d 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/file-line-audit/SKILL.md · 137 lines

How it starts

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

File Line Audit

使用这个技能审计仓库中的超长源码文件,只返回达到或超过指定行数阈值的文件。

使用时:

  • scripts/ 目录选择匹配当前操作系统和 CPU 架构的打包二进制。
  • 始终在目标仓库根目录运行,这样 .gitignore 才能正确生效。
  • 先查看仓库结构和语言栈,再决定扫描范围。
  • 通过命令行显式传入扫描参数;没有默认配置文件。
  • 先应用仓库 .gitignore,再应用额外的 exclude 规则。
  • 使用一个或多个 include glob 限定扫描范围。
  • 只输出物理行数大于等于阈值的文件。

安装

npx skills add bosens-China/my-skills/skills/file-line-audit

二进制选择

scripts/ 下选择对应平台的可执行文件:

  • Windows amd64: scripts/line-audit-windows-amd64.exe
  • Linux amd64: scripts/line-audit-linux-amd64
  • Linux arm64: scripts/line-audit-linux-arm64
  • macOS amd64: scripts/line-audit-darwin-amd64
  • macOS arm64: scripts/line-audit-darwin-arm64

步骤

  1. 确认当前位于目标仓库根目录。
  2. 检查仓库结构,决定扫描哪些内容:
    • 识别源码目录,例如 srcappappspkgpackageslibinternalcmdbackendfrontendclientserverserviceservicesapiweb
    • 识别相关源码扩展名,例如 jststsxvuepygorsjavaktrbphpcsswift
    • 仅在 .gitignore 不足时添加额外 exclude,例如 dist/build/coverage/ 或生成目录。
  3. 根据当前平台选择正确的 scripts/line-audit-* 二进制。
  4. Linux/macOS 下确保二进制可执行:
    chmod +x <binary_path>
    
  5. 使用显式 --include、可选 --exclude 和可选 --threshold 运行。
  6. 向用户返回超阈值文件列表。

命令

以下示例中,<skill_root> 是当前 skill 目录的绝对路径。

使用 include 参数运行

Unix-like 系统:

chmod +x <skill_root>/scripts/line-audit-<target>
<skill_root>/scripts/line-audit-<target> \
  --threshold 400 \
  --include "src/**/*.{ts,tsx,js,jsx,vue}" \
  --include "apps/**/*.{ts,tsx,js,jsx,vue}" \
  --exclude "dist/" \
  --exclude "build/"

Windows:

& <skill_root>\scripts\line-audit-windows-amd64.exe `
  --threshold 400 `
  --include "src/**/*.{ts,tsx,js,jsx,vue}" `
  --include "apps/**/*.{ts,tsx,js,jsx,vue}" `
  --exclude "dist/" `
  --exclude "build/"

使用 JSON 参数运行

如果完整参数对象更方便,使用 --json

<skill_root>/scripts/line-audit-<target> --json '{
  "threshold": 400,
  "include": [
    "src/**/*.{ts,tsx,js,jsx,vue}",
    "apps/**/*.{ts,tsx,js,jsx,vue}"
  ],
  "exclude": [
    "dist/",
    "build/"
  ]
}'

Read the full file on GitHub · 137 lines

Files

What ships with it

5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 12d ago First seen · 137 lines · 74 tokens per session scan A 11811fbc14a7

Subscribe to this mod's changes

file-line-audit is a skill published in the GitHub repository bosens-China/tc39-atlas (0 stars, last pushed yesterday), licensed MIT. It adds 74 tokens to every session and 1,377 once invoked, about $0.0004 per session on Opus 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-31.

Related

Other skills, from other repositories

triage-contributor-pr

Triage open pull requests from external contributors to prisma/prisma and produce a per-PR verdict with evidence. Use when a maintainer asks to triage, evaluate, assess, or review the queue of incoming contributor PRs, to decide whether a fork PR is safe to run CI on, to check whether a PR is in scope for its version…

prisma/orm · 131 tokens

review-implement-phase

Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.

prisma/orm · 38 tokens

review-triage-phase

Produces canonical review actions from fetched review state and renders action markdown. Use when the user wants only triage/action-planning for the review-framework workflow.

prisma/orm · 36 tokens

no-bare-casts

Writing as in TypeScript or TSX production code, modifying a file that contains a bare as cast, silencing a type error with a cast, encountering as unknown as, or reviewing a cast site.

prisma/orm · 52 tokens

performance-lint-rules

Performance review guidance for Oxc linter rule implementations. Use only when reviewing Rust rule code under crates/oxclinter/src/rules/ or when explicitly auditing those rules for performance improvements.

oxc-project/oxc · 45 tokens

output-eval-error-analysis

Systematically review workflow traces to identify failure modes before building evaluators. Use when starting an eval project, after significant pipeline changes, or when production quality drops.

growthxai/output · 38 tokens