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.
/plugin marketplace add mukilankarthik/self-awarenessnpx agentmods add plugins/mukilankarthik/self-awareness/engineering-disciplinegit clone --depth 1 https://github.com/mukilankarthik/self-awarenessWrote 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/mukilankarthik/self-awareness/engineering-discipline)<a href="https://agentmods.dev/plugins/mukilankarthik/self-awareness/engineering-discipline"><img src="https://agentmods.dev/badge/plugins/mukilankarthik/self-awareness/engineering-discipline.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
engineering-discipline 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 yesterday.
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": "engineering-discipline",
"source": "./engineering-discipline",
"description": "Behavioral guidelines that reduce common agent coding mistakes: think before coding, simplicity first, surgical diffs, goal-driven execution, and mandatory verification for data/BI work.",
"version": "1.0.0",
"author": {
"name": "Mukilan Karthik"
},
"homepage": "https://github.com/mukilankarthik/self-awareness",
"repository": "https://github.com/mukilankarthik/self-awareness",
"license": "MIT",
"keywords": [
"engineering-discipline",
"code-review",
"simplicity",
"data-verification",
"bi-engineering",
"goal-driven",
"behavioral"
],
"category": "productivity"
}What ships with it
1 file beside marketplace.json#engineering-discipline 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.
- yesterday First seen · 22 lines scan A 9eb7a7703151
engineering-discipline is a plugin published in the GitHub repository mukilankarthik/self-awareness (3 stars, last pushed 17d ago), licensed MIT. 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-09-03.
Other plugins, from other repositories
lid-experimental
Experimental LID skills with opt-in installation and explicit lifecycle (promotion or retirement). Layers on top of linked-intent-dev and arrow-maintenance.
linked-intent-dev
Structured design-before-code workflow: HLD → LLD → EARS specs → Implementation plan.
great-cto
You already have the agent. This is everything around it. greatcto runs Claude Code as a pipeline of 70 specialist agents — an independent model checks each stage before the next builds on it, spending caps refuse rather than warn, and three decisions stay yours: what gets built, how, and whether it ships.
superstack
Агентная система разработки: ведёт от фразы до доказанного куска через блокирующие гейты на плане и верификации, объясняет каждый вывод человеческим языком и доказывает работоспособность живым прогоном.
catalyst-foundry
Setup, maintenance, and compounding upkeep of the Catalyst framework and the thoughts/ knowledge base: framework diagnostics/repair (setup-catalyst), terminal launcher config (setup-warp), and research-doc curation (research-curate). Future home for the compound-engineering retro/learning loop.
catalyst-legacy
Pre-phase-agent (wave-based) orchestration workflow preserved as a documented fallback: oneshot, orchestrate, god, setup-orchestrate. Superseded by catalyst-dev's execution-core/phase-agent pipeline. Requires catalyst-dev (shared backing scripts).