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 tupe12334/instinct --skill smeacgit clone --depth 1 https://github.com/tupe12334/instinctWrote 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/tupe12334/instinct/smeac)<a href="https://agentmods.dev/skills/tupe12334/instinct/smeac"><img src="https://agentmods.dev/badge/skills/tupe12334/instinct/smeac/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/tupe12334/instinct/smeac"><img src="https://agentmods.dev/badge/skills/tupe12334/instinct/smeac.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.00024 | $0.02444 |
| Opus 5.5 | $0.00010 | $0.00978 |
| Sonnet 5.5 | $0.00005 | $0.00489 |
| Haiku 4.5 | $0.00002 | $0.00244 |
Grade A, and why
smeac 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 1mo 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 — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
smeac Briefing Format
Overview
smeac is a military operations briefing structure used to communicate complex plans clearly and completely. Adapted for business, project management, and high-stakes operational contexts.
| Section | What it covers |
|---|---|
| S | Situation |
| M | Mission |
| E | Execution |
| A | Administration/Logistics |
| C | Command/Communications |
smeac ensures every participant has full context (Situation), clear purpose (Mission), a concrete plan (Execution), the resources they need (Administration), and knows who to contact and who decides (Command).
Section Breakdowns
S — Situation
Set the full context so everyone understands why this matters and what environment they're operating in.
Include:
- What's happening in the broader environment (market, product, org)
- What the problem or opportunity is
- Key constraints or external pressures (time, competition, regulations)
- What we know vs what's uncertain
Goal: no one should need to ask "why are we doing this?" after reading Situation.
M — Mission
One clear sentence (or short paragraph) stating what must be accomplished and why. The mission is the single most important element — everything else serves it.
Formula: [Who] will [what action] in order to [why / intended effect] by [when].
Example: "The product team will ship the new onboarding flow by [date] in order to reduce Day-1 churn by 20%."
Rules:
- One mission — if you have two, run two briefings
- State both the task (what) and the purpose (why)
- Everyone in the room should be able to recite the mission from memory after the briefing
E — Execution
The plan. How the mission gets accomplished.
Structure for complex missions:
- Commander's intent (or leader's intent): the end state if the plan breaks down — what does success look like, even if we deviate from the plan?
- Concept of operations: overview of the approach (phases, sequence)
- Task assignments: who does what, with specific assignments per person or team
- Coordinating instructions: timing, rules of engagement, cross-team dependencies, shared standards
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.
- 1mo ago First seen · 212 lines · 24 tokens per session scan A 71e5fa8d7f19
smeac is a skill published in the GitHub repository tupe12334/instinct (1 stars, last pushed 2mo ago), licensed MIT. It adds 24 tokens to every session and 2,444 once invoked, about $0.0001 per session on Opus 5.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
thinking-theory-of-constraints
When throughput or latency is pipeline-limited, identify the single binding constraint and exploit, subordinate, elevate, then recheck—ignore non-constraints.
karpenter
Design, install, debug, review, plan capacity, audit scaling history, migrate from Cluster Autoscaler, and upgrade Karpenter v1.x on EKS. Covers NodePool, EC2NodeClass, NodeClaim, Spot diversity, disruption strategy, Pod Identity/IRSA, interruption queue, private clusters, AMI rotation, and GitOps integration. Use…
thinking-lindy-effect
Use when longevity of a non-perishable option matters. Treat survival duration as a remaining-life prior, then check domain drift before favoring the proven.
pr-review
Comprehensive PR review across six dimensions — cost impact, environment drift, ownership gaps, SOC 2 compliance, deprecated API / version hygiene, and rollback feasibility. Each mode inspects the diff and current file state, reports findings with severity, and recommends concrete fixes. Use when preparing a PR for…
azure
Azure identity (Workload Identity, OIDC, Entra ID), resource tagging, AKS platform patterns, RBAC scoping, and production-readiness review — with Terraform generation.
kubescape
Check Kubernetes manifests, Helm charts, Kustomize overlays and live clusters against NSA-CISA, MITRE ATT&CK, CIS (EKS, AKS, GKE, vanilla) and SOC2 with the Kubescape CLI. Covers framework choice, score and severity gates, PR gates that fail only on new findings (--baseline), exceptions that actually suppress…