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 agentmods add skills/typiqally/lintropy/skillnpx skills add Typiqally/lintropy --skill skillgit clone --depth 1 https://github.com/Typiqally/lintropyWrote 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/typiqally/lintropy/skill)<a href="https://agentmods.dev/skills/typiqally/lintropy/skill"><img src="https://agentmods.dev/badge/skills/typiqally/lintropy/skill.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.06657 |
| Opus 5 | $0.00000 | $0.03328 |
| Sonnet 5 | $0.00000 | $0.01331 |
| Haiku 4.5 | $0.00000 | $0.00666 |
Grade A, and why
skill 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 4d 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.
This is a copy
100% identical to lintropy — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 672 lines — stays where its author put it; the contents beside it link to each section on GitHub.
version: 0.3.0
1. What lintropy is
lintropy is a YAML-configured, agent-first linter. Rules live in
lintropy.yaml (root) and .lintropy/<id>.rule.yaml (one rule per file).
Two rule kinds: query rules (tree-sitter S-expressions, AST-precise)
and match rules (regex, phase 2). Query rules support autofix via a
fix: field that interpolates {{captures}} into the @match span.
Diagnostics are rustc-styled text by default, JSON on --format json.
Exit codes: 0 clean, 1 diagnostics ≥ fail_on, 2 config/parse
failure, 3 internal crash.
Trigger phrases (if the user says any of these, reach for this skill):
- "write a lintropy rule"
- "add a lintropy rule / lint"
- "lintropy diagnostic"
- mention of
.rule.yamlor.rules.yaml - "ban with lintropy"
- "enforce in CI"
2. Commands
lintropy check # default; lint the repo
lintropy check --fix # apply autofixes in place
lintropy check --fix-dry-run # print unified diff, exit 0
lintropy check --format json -o report.json # machine-readable
lintropy explain <rule-id> # message, query, fix, source
lintropy rules [--format json] # list loaded rules
lintropy ts-parse <file> [--lang <name>] # dump S-expression (auto-detects by extension)
lintropy config validate # schema + queries, no run
lintropy init [--with-skill] # scaffold config; install SKILL
lintropy schema # JSON schema for the config
Exit codes (§7.6):
| code | meaning |
|---|---|
| 0 | no diagnostics at/above fail_on |
| 1 | diagnostics present at/above fail_on |
| 2 | config load / schema / parse failure |
| 3 | internal error |
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.
- 4d ago First seen · 672 lines · 0 tokens per session scan A a0b041c925c1
skill is a skill published in the GitHub repository Typiqally/lintropy (5 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 6,657 tokens. A static security scan graded it A with 0 findings. It is 100% identical to lintropy, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
implement
Research, implement, test, document, and review a Fallow feature, fix, refactor, or repository improvement. Use when asked to build or change Fallow.
open-draft-pr
Prepare local changes for review with an intentional commit, push, and ready PR for fallow. Use when the user wants to publish work, open a PR, or turn local changes into a reviewable branch.
setup
Set up or update TDD Guard for the current project. Detects the test framework, installs or updates the matching reporter, and configures or migrates its configuration to match the current specification.
browser-smoke-review
Use browser automation to review docs pages, preview URLs, rendered output, or web-facing fallow surfaces. Use when the user wants a screenshot-based review, browser smoke test, docs site check, or preview deployment inspection.
debug-false-positive
Diagnose and fix a Fallow false positive or false negative through extraction, resolution, graph, analysis, reporting, and real-consumer verification.
panel-review-loop
Iteratively review and improve a Fallow user-facing surface across representative real-world projects until the panel has no blocking concerns.