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/mishahanin/heading-os-marketplaceWrote 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/plugins/mishahanin/heading-os-marketplace/heading-ops)<a href="https://agentmods.dev/plugins/mishahanin/heading-os-marketplace/heading-ops"><img src="https://agentmods.dev/badge/plugins/mishahanin/heading-os-marketplace/heading-ops/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/plugins/mishahanin/heading-os-marketplace/heading-ops"><img src="https://agentmods.dev/badge/plugins/mishahanin/heading-os-marketplace/heading-ops.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
heading-ops 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 2mo 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
{
"name": "heading-ops",
"description": "Ops and thinking: draft an implementation plan (create-plan), reason through a hard decision (deep-think), and run a structural editorial pass (editorial-review). Reserved (data/daemon/key-bound): dashboard, radar, queue, sync, next, recall, council.",
"author": {
"name": "Misha Hanin",
"email": "[email protected]"
}
}
What it installs
The manifest is a name and a version. 3 skills travel with it, and installing the plugin installs all of them — 328 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 2mo ago First seen · 9 lines scan A 4015d5ce3037
heading-ops is a plugin published in the GitHub repository mishahanin/heading-os-marketplace (2 stars, last pushed 1mo ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
gh-review-loop
Clears AI reviewer feedback on your PR: reads real review-thread state, sweeps the sibling instances the reviewer missed, gates every push on your repo's own tests, then requests re-review — hard-capped at 3 re-review requests. Claude Code, Codex, Gemini and Copilot built in; any reviewer bot can be configured.
gates
Three stateless PreToolUse gates, a PostToolUse JSON-config guard, a 1Password signing nudge, and a docs-consolidation trigger. Denies a git commit that changes code without staging its covering docs (per-plugin README/CLAUDE.md pairs, or the nearest README/CLAUDE/AGENTS walking up); denies a high-fan-out Workflow…
writing-artifacts
Positive writing system for durable written artifacts — READMEs, ADRs, PR descriptions, docs, runbooks. Reader-expectation prose, Diátaxis document jobs, plain-language structure. Plus a readme skill: fact inventory, first-screen and funnel checks, and a checker for broken paths, links, anchors, commands and badges.
codex-review
Cross-provider adversarial plan/design-doc review via OpenAI Codex (GPT-6 Sol) plus a blind Opus reviewer: verdict-loop protocol, atomic chain guard, cross-repo decision-gate log.
domain-modeling
Actively build and sharpen a project's ubiquitous language — an opinionated CONTEXT.md glossary — by challenging terms, disambiguating overloaded words, and stress-testing domain relationships. Adapted from mattpocock/skills (MIT).
handoff
Manual /handoff skill — writes a structured resume doc on demand, auto-loads it on next session.