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/eduardohki/code-agent-plugins/gleam-idiomsnpx skills add eduardohki/code-agent-plugins --skill gleam-idiomsgit clone --depth 1 https://github.com/eduardohki/code-agent-pluginsWrote 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/eduardohki/code-agent-plugins/gleam-idioms)<a href="https://agentmods.dev/skills/eduardohki/code-agent-plugins/gleam-idioms"><img src="https://agentmods.dev/badge/skills/eduardohki/code-agent-plugins/gleam-idioms.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.00133 | $0.01053 |
| Opus 5 | $0.00067 | $0.00526 |
| Sonnet 5 | $0.00027 | $0.00211 |
| Haiku 4.5 | $0.00013 | $0.00105 |
Grade A, and why
gleam-idioms 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 5d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gleam Idioms: Conventions, Patterns & Anti-patterns
Distilled from the official guide (https://gleam.run/documentation/conventions-patterns-and-anti-patterns) so idiomatic Gleam norms are on hand without re-deriving them from scratch.
Scope is that guide: naming, module and namespace layout, error modeling, and the
listed patterns and anti-patterns. Syntax-level idiom (use expressions, |>
pipelines, labelled arguments) is out of scope and not covered here.
How to use
When writing or reviewing Gleam, scan the quick-reference tables below and apply the rule directly when the one-line gloss is enough. When a decision needs the code example or the rationale (modeling errors, sans-io/builder shape, namespace layout, why to avoid a catch-all), load the matching reference file before acting:
references/conventions.md: the 10 style/structure conventions.references/patterns.md: 6 design patterns worth reaching for.references/anti-patterns.md: 10 things to avoid, each with the fix.
Do not load all three by reflex; open the one that covers the decision at hand.
Conventions (quick reference)
| Convention | Rule |
|---|---|
| Qualified imports | Import modules; call module.fn, not bare fn. |
| Annotate functions | Type-annotate every arg and return, public and private. |
| Result for failure | Fallible functions return Result; Nil error when no info needed. |
| Singular module names | user, not users, in every path segment. |
| Acronyms as words | Json/Http, not JSON/HTTP. |
x_to_y conversions |
Drop the type prefix when the module is named after the type. |
try_ prefix |
Name the Result-handling variant try_map, etc. |
| Use core libraries | Depend on official gleam_* packages; don't reimplement. |
| Config in gleam.toml | Dev-tool config under tools.$TOOL keys, not stray files. |
| Source directories | src/ (deps + src only), test/ and dev/ (anywhere). |
Patterns (quick reference)
| Pattern | Use it to |
|---|---|
| Descriptive errors | Give error variants domain names + fields (incl. cause). |
| Comment liberally | Explain what and why. |
| Make invalid states impossible | Model rules as variants so bad data can't be built. |
| Replace bools with custom types | Named states document intent and leave room to grow. |
| Sans-io | Split clients into request-builder + response-parser; no I/O. |
| Builder | new(required) then optional modifier fns returning copies. |
What ships with it
3 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.
- 5d ago First seen · 85 lines · 0 tokens per session scan A 0b3a71502125
gleam-idioms is a skill published in the GitHub repository eduardohki/code-agent-plugins (2 stars, last pushed 17d ago), licensed MIT. It adds 133 tokens to every session and 1,053 once invoked, about $0.0007 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
matlab
Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.
ast-grep
Guide for writing ast-grep rules to perform structural code search and analysis. Use when users need to search codebases using Abstract Syntax Tree (AST) patterns, find specific code structures, or perform complex code queries that go beyond simple text search. This skill should be used when users ask to search for…
platform-detection
Identify a .NET project's test platform, framework, command mode, and SDK-style vs classic project system. Use only for "which test platform/framework?", "VSTest or MTP?", or "what runner does this project use?", including bridge settings, UseVSTest opt-outs, and incompatible or conflicting VSTest/MTP configuration.…
unity-version-split
Split a C# file into Unity 6.5+ and pre-Unity 6.5 variants. Use when a file needs different implementations for different Unity versions due to API changes (e.g., EntityId vs int, GetEntityId vs GetInstanceID).
rust-pro
Master modern Rust (2024 edition) with async patterns, advanced type system features, and production-ready systems programming. Expert in the current Rust ecosystem including Tokio, axum, and modern crates. Use PROACTIVELY for Rust development, performance optimization, or systems programming.
omh-rust
This is a Hermes-native rust workflow skill.