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.
git clone --depth 1 https://github.com/alinaqi/maggyWrote 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/commands/alinaqi/maggy/build-in-public)<a href="https://agentmods.dev/commands/alinaqi/maggy/build-in-public"><img src="https://agentmods.dev/badge/commands/alinaqi/maggy/build-in-public/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/commands/alinaqi/maggy/build-in-public"><img src="https://agentmods.dev/badge/commands/alinaqi/maggy/build-in-public.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.00019 | $0.00293 |
| Opus 5 | $0.00010 | $0.00147 |
| Sonnet 5 | $0.00004 | $0.00059 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
build-in-public 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 11d 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.
What it actually says
Build-in-Public Commands
Enable for this project
To enable the build-in-public plugin for the current project:
/build-in-public enable
This activates post generation for significant work events: PR merged, feature shipped, review passed.
Manage brands
By default, ALL company names are anonymized. To explicitly allow a brand:
/build-in-public add brand Protagé
/build-in-public add brand edubites
Brands added this way appear by name in posts. Everything else stays anonymized.
Manage clickouts
To add a URL that gets appended to posts (especially X/Twitter):
/build-in-public add clickouts to https://github.com/alinaqi/maggy
/build-in-public add clickouts to https://edubites.ai
Multiple URLs are supported. X posts always include the first clickout.
Customization file
Your guidelines are stored in the plugin's customization.md file. When you change a setting via slash command, it updates this file:
~/.maggy/plugins/build-in-public/customization.md
The plugin reads this file on every post generation — no restart needed.
Disable
/build-in-public disable
Pauses post generation for the current project.
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.
- 11d ago First seen · 56 lines · 19 tokens per session scan A aaf902dbe21e
build-in-public is a command published in the GitHub repository alinaqi/maggy (707 stars, last pushed 2d ago), licensed MIT. It adds 19 tokens to every session and 293 once invoked, about $0.0001 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 commands, from other repositories
frappe-backend
Treat the task as Frappe backend work.
sdd-explore
Explore and investigate an idea or feature — reads codebase and compares approaches.
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
gentle-sdd-ff
Fast-forward all SDD planning phases — proposal through tasks.
ijfw-audit
Run the IJFW audit gate for the current workflow phase. Usage: /ijfw-audit [phase name].
atomic-plan
Write a design doc (concepts, business rules, approaches) and a checkpoint-table spec (contract) for non-trivial work; inline spec only for trivial. Gauges triviality; loops spec authoring with subagents. Human-facing artifact, Mermaid diagrams allowed.