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.
npx skills add bosens-China/tc39-atlas --skill file-line-auditgit clone --depth 1 https://github.com/bosens-China/tc39-atlasWrote 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.
[](https://agentmods.dev/skills/bosens-china/tc39-atlas/file-line-audit)<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.
<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>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.
| Model | Per session | Once 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 |
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.
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规则。 - 使用一个或多个
includeglob 限定扫描范围。 - 只输出物理行数大于等于阈值的文件。
安装
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
步骤
- 确认当前位于目标仓库根目录。
- 检查仓库结构,决定扫描哪些内容:
- 识别源码目录,例如
src、app、apps、pkg、packages、lib、internal、cmd、backend、frontend、client、server、service、services、api、web。 - 识别相关源码扩展名,例如
js、ts、tsx、vue、py、go、rs、java、kt、rb、php、cs、swift。 - 仅在
.gitignore不足时添加额外exclude,例如dist/、build/、coverage/或生成目录。
- 识别源码目录,例如
- 根据当前平台选择正确的
scripts/line-audit-*二进制。 - Linux/macOS 下确保二进制可执行:
chmod +x <binary_path> - 使用显式
--include、可选--exclude和可选--threshold运行。 - 向用户返回超阈值文件列表。
命令
以下示例中,<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/"
]
}'
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.
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.
- 12d ago First seen · 137 lines · 74 tokens per session scan A 11811fbc14a7
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.
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…
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.
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.
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.
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.
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.