Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add metraton/gaia/plugin install gaiaWrote 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/metraton/gaia/blog-writing)<a href="https://agentmods.dev/skills/metraton/gaia/blog-writing"><img src="https://agentmods.dev/badge/skills/metraton/gaia/blog-writing/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/metraton/gaia/blog-writing"><img src="https://agentmods.dev/badge/skills/metraton/gaia/blog-writing.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.00020 | $0.01151 |
| Opus 5 | $0.00010 | $0.00575 |
| Sonnet 5 | $0.00004 | $0.00230 |
| Haiku 4.5 | $0.00002 | $0.00115 |
Grade A, and why
blog-writing 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.
How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Blog Writing
Jorge's blog (metraton.github.io) is where he thinks out loud about agentic systems, context engineering, and the intersection of architecture and AI. The articles are bilingual (English and Spanish), grounded in real experience, and written in first person. They are not corporate content -- they are reflections from someone building these systems daily.
The Writing Process
1. Find the story first
Every article starts with something that actually happened -- a deployment that went sideways, a late-night refactor, a conversation that shifted your thinking. The story is the anchor. Without it, you are writing a tutorial, not an article.
Ask Jorge: "What happened recently that surprised you or changed how you think about something?" The best topics come from moments where the outcome was different from the expectation.
2. Build the brief
Before writing a single paragraph, define: title, audience, core thesis (one sentence), and format. Jorge's natural format is Strategic Insight -- personal experience analyzed through a technical lens, ending with a transferable lesson.
The audience is engineers, solution architects, AI practitioners, and tech leaders. They do not need hand-holding but they appreciate honesty about what did not work.
3. Draft in Markdown, iterate with Jorge
Write the first draft in Markdown at /home/jorge/ws/me/<slug>.md. Work section by section -- do not dump an entire draft and ask "what do you think?" Each section should be reviewed before moving to the next.
Article structure (not rigid, but this is Jorge's natural flow):
- Opening story -- what happened, told personally
- The problem -- what was broken or surprising
- Investigation -- what you looked into and found
- The shift -- the insight or reframe
- In practice -- what changed, concretely
- Results -- evidence it worked
- Closing thought -- punchy, memorable, one line
4. Principles that matter
Examples must be real. Not "imagine a team that..." but "I was deploying to Cloud Run when..." If you cannot point to something that actually happened, the example does not belong.
What ships with it
1 file 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.
- 11d ago First seen · 96 lines · 20 tokens per session scan A 528ea584f9fa
blog-writing is a skill published in the GitHub repository metraton/gaia (3 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 1,151 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-31.
Other skills, from other repositories
review-team
A multi-reviewer code review process that checks a change from several specialist viewpoints and combines the results into one report. It can cover bugs, security, tests, dependencies, frontend behavior, and continuous-integration workflows.
ultra
Fans the work out as a fleet of parallel Grok and Codex agents billed to their own subscriptions, then synthesizes one result. The peer engine equivalent of ultracode, adding intensity without spending Claude quota on the fleet. Use it for genuinely broad goals, not only explicit asks for intensity.
grok-prompting
Brief writing guidance for composing self contained Grok briefs for coding, review, diagnosis, and second opinion tasks.
smoke
Runs a three probe live smoke wave after a plugin update and reports gate chain health before real work rides it.
codex-result-handling
Internal contract for returning Codex companion output without alteration.
shipwrights-loop
Drive multiple Jira tickets sequentially through the /shipwrights-epic pipeline. Auto-picks the next ticket, watches the PR until merged, transitions Jira to shipped, repeats. Resumable across Claude Code sessions via .shipwrights/loop-state.json. Invoked as /shipwrights-loop [N] | --status | --abort.