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 antropos17/Aegis --skill aegis-contextgit clone --depth 1 https://github.com/antropos17/AegisWrote 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/antropos17/aegis/aegis-context)<a href="https://agentmods.dev/skills/antropos17/aegis/aegis-context"><img src="https://agentmods.dev/badge/skills/antropos17/aegis/aegis-context/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/antropos17/aegis/aegis-context"><img src="https://agentmods.dev/badge/skills/antropos17/aegis/aegis-context.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.00034 | $0.00413 |
| Opus 5.5 | $0.00014 | $0.00165 |
| Sonnet 5.5 | $0.00007 | $0.00083 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
aegis-context 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 today.
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
AEGIS source navigation
Start with docs/development/current-context.md in the selected checkout. It
owns checkout selection, current entrypoints, evidence limits and history routing.
If working on an older revision without it, read that checkout's AGENTS.md,
package.json, Vite and TypeScript configs and record HEAD and dirty state.
Resolve source paths against that checkout, never the skill installation folder.
For a source question, follow imports and actual callers from the configured
entrypoint. In main, inspect platform/index.js for OS dispatch and preload.js
with the handler and renderer consumer for IPC. Use rule-loader.js and its
callers to identify rule consumers. Read only the affected historical entries
through memory-bank/README.md; preserve dated receipts and active parallel work.
Derive maintained counts with npm run counts:check and versions from package
files. Check effective checkJs/include and per-file directives before describing
type coverage. For generated inventory scope and optional dependency graphs,
read the relevant sections of docs/development/workflow.md. Direct test imports
and static graphs locate candidates; they do not establish behavioral coverage
or complete runtime reachability.
When Serena is connected, activate the exact checkout by absolute path and verify its active project before symbol queries. Use symbol definitions/references for large files and literal search for IPC strings and computed CommonJS paths. Svelte mode includes JS/TS. A configured server is not proof of a connection.
Use design-system for interface work, electron-main for main-process changes, svelte-patterns for Svelte and testing for harness decisions. Commit/PR workflows remain separate and follow the requested scope. For skill-routing evaluation, read trigger cases; they are examples, not tasks or evidence that an agent evaluation ran.
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.
- today First seen · 37 lines · 34 tokens per session scan A cea44680addd
aegis-context is a skill published in the GitHub repository antropos17/Aegis (157 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 413 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-10-17.
Other skills, from other repositories
eac-desktop-tips
A quick reference for using and troubleshooting features in the Deepseek Harness EAC desktop client. It covers window behavior, conversation rollback, plugins, desktop pets, Skills, MCP services, updates, and logs.
electron-expert
Expert in Electron framework, desktop app development, IPC, and cross-platform packaging. Use when the user mentions desktop, Node.js, cross platform, Windows, macOS, or Linux, or when the task involves Electron Architecture, Process Types, IPC Communication, or App Lifecycle.
acr-agent-registry
Behavioral registry for AI agents. Log interactions, build an interaction profile, query it through lenses (friction, coverage, stable corridors, failure registry, trend), and receive anomaly signal notifications if ACR observes elevated signals on a component in your composition.
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
generate-run-commands
Generate or modify run commands for the current session. Use when the user wants to set up or update run commands that appear in the session's Run button.
create-canvas
Create a project Copilot extension canvas for the current workspace.