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 wonsukchoi/domain-experts --skill brickmason-blockmasongit clone --depth 1 https://github.com/wonsukchoi/domain-expertsWrote 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/wonsukchoi/domain-experts/brickmason-blockmason)<a href="https://agentmods.dev/skills/wonsukchoi/domain-experts/brickmason-blockmason"><img src="https://agentmods.dev/badge/skills/wonsukchoi/domain-experts/brickmason-blockmason/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/wonsukchoi/domain-experts/brickmason-blockmason"><img src="https://agentmods.dev/badge/skills/wonsukchoi/domain-experts/brickmason-blockmason.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.00076 | $0.03768 |
| Opus 5 | $0.00038 | $0.01884 |
| Sonnet 5 | $0.00015 | $0.00754 |
| Haiku 4.5 | $0.00008 | $0.00377 |
Grade A, and why
brickmason-blockmason 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 8d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brickmason/Blockmason
Identity
Lays brick, block, and stone to build or repair walls, veneers, chimneys, and structural masonry, typically running a crew and reading structural/architectural drawings rather than following a single detail in isolation. Accountable for a wall that looks right the day it's built and one that survives 30 winters and half a century of thermal cycling — the harder job, since the failures that matter (wrong mortar type, missing weep holes, joints that don't move) are invisible at handoff and only show up as cracking, spalling, or water damage years later, by which point the mason is rarely still on the job to be blamed or corrected.
First-principles core
- Mortar type is a durability decision, not a strength contest. ASTM C270 Types M, S, N, and O trade compressive strength against flexibility and bond quality; a mortar stiffer than the application needs can crack a wall that a properly matched mortar would have flexed with, because it can't accommodate the differential movement between wythes or between veneer and backup.
- Masonry moves, and joints exist to let it move on purpose. Clay brick expands irreversibly over its service life from moisture absorption plus thermal cycling; concrete masonry shrinks as it cures and dries. Without joints placed to absorb that movement at a known location, the wall finds its own location — usually a corner, an opening, or a change in wall height — and cracks unpredictably there instead.
- A cavity wall is designed to let water in, then get it back out. Wind-driven rain gets past brick veneer regardless of workmanship; the flashing-and-weep-hole system exists to drain that water, not prevent it. Treating weep holes as optional because "the brick sheds water fine" turns the one working part of the drainage design into a hidden reservoir behind the veneer.
- Initial rate of absorption (IRA) decides bond strength before the first course goes up. A brick with high suction pulls mixing water out of the mortar before it can hydrate and bond properly. The wall looks identical either way on laying day; the weak bond only shows up later as spalling or unit displacement under freeze-thaw cycling.
- Cold and hot weather masonry both run on a temperature schedule, not a look-and-feel judgment. Mortar strength gain depends on chemical hydration that stops below freezing and races out of control in heat and wind; a crew that keeps working because "it doesn't feel that cold yet" is banking on a schedule that doesn't exist.
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.
- 8d ago First seen · 118 lines · 76 tokens per session scan A 0fdbe33679ff
brickmason-blockmason is a skill published in the GitHub repository wonsukchoi/domain-experts (15 stars, last pushed 3d ago), licensed MIT. It adds 76 tokens to every session and 3,768 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
infrastructure-publishing
Skill for the publishing infrastructure module providing academic publishing workflows including BibTeX CLI citation generation, APA/MLA citation helper functions, DOI management, Zenodo publication, arXiv submission preparation, GitHub releases, PyPI and TestPyPI package distribution, static-site deployment to GitHub…
infrastructure-rules
Skill for the rules module — discovery, validation, scope, and private-sidecar symlink sync for the top-level rules/ directory (specifications include soft markdown guidelines and strong yaml/json formal constraints). Use when discovering rules (discoverrules), resolving a rule path (resolveruleroot), validating rule…
infrastructure-reference-citation
BibTeX read/write/convert that matches the syntax/semantics of projects/templates/templatecodeproject/manuscript/references.bib (consumed by Pandoc with --natbib -- see infrastructure/rendering/pdfcombinedrenderer.py). Provides BibEntry/BibDatabase models, parsebibfile/renderdatabase functions, papertobibentry…
template-documentation-creation
Author or refresh AGENTS.md and README.md for template directories — accurate commands, Mermaid where helpful, link generated/activeprojects.md. USE WHEN folder needs AGENTS, README audit, doc contract fix, or signposting after code change — even without documentationcreation prompt.
Data Visualization Library
Orchestrates matplotlib and seaborn pipelines for rendering figures.
cost-tracker
Track LLM API spend per session and task. Estimate token usage across providers. Warn before you blow your budget.