Borrowing it
Nothing to install: this file belongs to 363045841/KLineChartQuant. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/363045841/KLineChartQuant/main/.opencode/skills/fallow-check/SKILL.mdgit clone --depth 1 https://github.com/363045841/KLineChartQuantWrote 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/363045841/klinechartquant/fallow-check)<a href="https://agentmods.dev/skills/363045841/klinechartquant/fallow-check"><img src="https://agentmods.dev/badge/skills/363045841/klinechartquant/fallow-check/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/363045841/klinechartquant/fallow-check"><img src="https://agentmods.dev/badge/skills/363045841/klinechartquant/fallow-check.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.00050 | $0.00690 |
| Opus 5.5 | $0.00020 | $0.00276 |
| Sonnet 5.5 | $0.00010 | $0.00138 |
| Haiku 4.5 | $0.00005 | $0.00069 |
Grade A, and why
fallow-check 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 18d 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.
What it actually says
Fallow 常用流程
硬规则
- 统一
fallow <子命令> [范围 flag] --format json --quiet，不加--pretty。 - stderr 与 stdout 分开，禁止
2>&1合并。 - exit
0=干净、1=有 findings，两者都是成功结果；其它才是配置/网络/资源错误。
常用命令
| 目的 | 命令 |
|---|---|
| 审计本次改动 | fallow audit --base HEAD~1 --format json --quiet |
| 只看某一类问题 | fallow dead-code --circular-deps --unused-exports --format json --quiet |
| 只看改动文件 | fallow dead-code --changed-since HEAD~1 --format json --quiet |
| 循环依赖 / 边界 | fallow architecture --cycles --format json --quiet |
| 重复代码 | fallow dupes --format json --quiet |
| 复杂度热点 | fallow health --hotspots --targets --format json --quiet |
| 删之前取证 | fallow dead-code --trace <file>:<export> --format json --quiet |
| 自动修复 | fallow fix --dry-run --format json --quiet <path> → fallow fix --yes --format json --quiet <path> |
| 查某 issue 是什么 | fallow explain unused-export --format json |
坑
fix的范围只能靠位置参数[PATH]收敛，--changed-since不生效。不限定就全仓跑，会误删 web-component 构建入口导出，以及@vue/test-utils/@babel/*这类被配置文件引用的依赖。fix只处理 unused export / dependency / enum member，不处理 unused type，那类要手删。audit默认--gate new-only，只卡新引入的问题；继承问题仅作 JSON 上下文。全部计入用--gate all。--type-aware走 TypeScript checker，约 50s，按需再开。- 假阳性先
grep复核再删；属于公开 API（包exports里导出）的成员默认保留。
本仓库
- 已
pnpm add -g fallow，直接用fallow，不必npx -y。 - 配置在
.fallowrc.json（entry / ignorePatterns / rules / ignoreDependencies）。 - 建议补
ignoreDependencies: ["~icons"]（unplugin-icons 虚拟模块）。 - 完整能力（plugins、coverage、impact、migrate 等）见
.agents/skills/fallow/。
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.
- 18d ago First seen · 41 lines · 50 tokens per session scan A f72f5de911b7
fallow-check is a skill published in the GitHub repository 363045841/KLineChartQuant (37 stars, last pushed today), licensed Apache-2.0. It adds 50 tokens to every session and 690 once invoked, about $0.0002 per session on Opus 5.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-10-12.
Other skills, from other repositories
agent-upkeep
Perform one small, scoped maintenance improvement to the Elements monorepo and open a single reviewable pull request. Use this skill for scheduled or unattended upkeep runs that improve unit test coverage for one file, fix one behavioral bug in one module, or move one off ESLint rule toward enforcement to reduce…
agent-debug-ci
Investigate failed scheduled or nightly GitHub Actions runs on the default branch, determine whether the failure is reproducible and repository-owned, implement the smallest evidence-backed fix, validate it, and open a pull request. Use when a failed nightly CI event starts an agent, or when the standard CI or…
review
Review one pull request for real bugs, regressions, and convention violations. Enumerate candidate issues across the whole diff, verify each against the code, then return structured line-anchored findings and a verdict. Read-only on GitHub; the orchestrator posts the review.
adversarial-reviewer
Stress-test a code change for concrete correctness defects, unsafe assumptions, and failure modes. Use when the user explicitly asks for an adversarial review, a deep bug hunt, or to tear a change apart, or to check your own change before submitting it. Do not use for ordinary review, style feedback, or general…
establishing-code-ownership
Determine which PostHog team owns a file, directory, or code path, or enumerate all code a team owns (via distributed owners.yaml, products//product.yaml, and .github/CODEOWNERS). Use when assigning a reviewer, attributing a bug or slow query to a team, routing work, scoping a team-wide audit, or answering "who owns…
extending-hobby-smoke-tests
Design, extend, review, or debug PostHog Hobby end-to-end smoke tests in bin/hobby-ci.py and .github/workflows/ci-hobby.yml. Use when adding an ingestion round trip, deciding whether a product belongs in Hobby CI, changing the CI Hobby service topology or API-key scopes, or diagnosing a smoke test that captures data…