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.5 | $0.00069 | $0.00999 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (51 stars, last pushed 23d ago), licensed MIT. It adds 173 tokens to every session and 2,497 once invoked, about $0.0007 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-08-30.
Other skills, from other repositories
ring:migrating-to-lib-observability
Migrating a Lerian Go app off lib-commons observability imports (deprecated shims or removed APIs) to lib-observability via a fixed mapping table, then bumps go.mod and validates the build; ring:backend-go applies the edits. Covers log/zap/runtime/assert, opentelemetry/tracing, HTTP middleware, context helpers, and…
ring:using-lib-streaming
Using lib-streaming, Lerian's producer-only event publication library (Kafka/SQS/RabbitMQ/EventBridge), in two modes. Sweep Mode detects DIY publishers (franz-go, sarama, amqp091, watermill, raw AWS SDK) and re-rolled manifests/breakers. Reference Mode catalogs the Builder/Emitter/Catalog facade. Companion to…
ring:using-lib-systemplane
Using lib-systemplane, the hot-reload runtime-config plane (Postgres LISTEN/NOTIFY or MongoDB change streams), in two modes. Sweep Mode detects DIY config reload (SIGHUP, fsnotify, viper, pgx LISTEN), manual tenant-scoping, hand-built admin CRUD, and v4 residue. Reference Mode catalogs client lifecycle and…
ring:using-lib-observability
Using lib-observability v1.1.0, Lerian's OpenTelemetry foundation (lib-commons, lib-systemplane, lib-streaming depend on it), in two modes. Sweep Mode detects DIY zap/slog logging, raw OTel metrics, hand-rolled redaction, and hard-coded attribute strings. Reference Mode catalogs the log, metrics, zap, redaction, and…
ring:using-outbox
Using the transactional-outbox pattern across lib-streaming (writer) and lib-commons/v5/commons/outbox (repository + relay), in two modes. Sweep Mode detects DIY outbox tables, hand-rolled relay loops, send-and-pray emits, missing WithOutboxTx wrapping, and broker calls inside DB transactions. Reference Mode catalogs…
ring:using-tracing
Using lib-observability/tracing for OTEL provider lifecycle, trace-context propagation across HTTP/gRPC/queues, span error/event recording, and PII redaction, in two modes. Sweep Mode detects raw OTEL setup, hand-rolled header propagation, manual span-attribute assembly, and DIY redaction. Reference Mode catalogs…