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 get-tmonier/argot --skill argot-suggest-rulesgit clone --depth 1 https://github.com/get-tmonier/argotWrote 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/get-tmonier/argot/argot-suggest-rules)<a href="https://agentmods.dev/skills/get-tmonier/argot/argot-suggest-rules"><img src="https://agentmods.dev/badge/skills/get-tmonier/argot/argot-suggest-rules/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/get-tmonier/argot/argot-suggest-rules"><img src="https://agentmods.dev/badge/skills/get-tmonier/argot/argot-suggest-rules.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00173 | $0.02497 |
| Opus 5 | $0.00086 | $0.01248 |
| Sonnet 5 | $0.00035 | $0.00499 |
| Haiku 4.5 | $0.00017 | $0.00250 |
Grade A, and why
argot-suggest-rules 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 10d 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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
argot-suggest-rules
argot-write-rule starts from a convention you state. This skill starts from
what argot already found in the repo. argot conventions mines two kinds:
- placement conventions — where a kind of code lives: a feature (a call, an
import) that concentrates in one location (a directory, a filename role, an
extension) and is near-absent elsewhere. "validation lives in schema files",
"
queryInterfaceonly in migrations", "business logic in the service layer, not in views". These are the team's structural rules. - vocabulary — the repo's own most-used internal API (shared helpers, the objects everyone routes through).
The mining is corpus- and framework-agnostic (pure feature×location
association) and every candidate carries its evidence. You turn a chosen one
into a real scripted rule — same manifest + Rhai + fixture-gate shape as
argot-write-rule, same custom group. Full reference:
https://argot.tmonier.com/docs/custom-rules/.
This is a deliberate later workflow after audit and ordinary check activation; it does not make a discovered convention a default CI or commit gate. It is assisted authoring, not rule generation or lifecycle wiring: a user still chooses the convention, reviews the rule, and configures any workflow that runs it.
Preconditions
argot --version— if missing, tell the user how to install it (https://argot.tmonier.com/docs/getting-started/) and stop.argot conventionsneeds a complete, committed, fresh fit snapshot. Runargot status --format json; ifsnapshot.completeorsnapshot.committedis false, stop and finish argot-setup first. If the config is out of sync or refresh is recommended, hand off to argot-refresh on the accepted branch; it reviews scope and mutes before the local fit and committed.argot/update. Do not fit implicitly: mixing fitted vocabulary with a newer live placement catalog would codify an incoherent convention.
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.
- 10d ago First seen · 199 lines · 173 tokens per session scan A baa6350843a9
argot-suggest-rules is a skill published in the GitHub repository get-tmonier/argot (48 stars, last pushed today), licensed MIT. It adds 173 tokens to every session and 2,497 once invoked, about $0.0009 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-30.
Other skills, from other repositories
boundary-validation
This skill should be used when the user asks to "validate input", "parse request data", "handle form data", "add Zod schema", "sanitize user input", or creates API endpoints and system boundaries. Provides parse-don't-validate patterns with schema validation for type-safe boundary enforcement and hostile input defense.
consistency
This skill should be used when reviewing code for naming convention violations, pattern deviations, or inconsistent API styles.
documentation
This skill should be used when reviewing for documentation drift, missing API docs, or stale comments.
java
This skill should be used when the user works with Java files (.java), asks about "records", "sealed classes", "Optional", "streams", "composition over inheritance", or discusses modern Java patterns and API design. Provides patterns for type system usage, error handling, immutability, and concurrency.
patterns
This skill should be used when the user asks to "create an API endpoint", "add CRUD operations", "implement event handlers", "set up logging", "add configuration", or builds features involving database operations, REST/GraphQL APIs, pub/sub patterns, or service configuration. Provides implementation patterns that…
typescript
This skill should be used when the user works with TypeScript files (.ts/.tsx), asks about "generics", "type guards", "utility types", "strict typing", "discriminated unions", or discusses type safety and inference. Provides patterns for Result types, exhaustive checks, branded types, and type-safe API contracts.