Borrowing it
Nothing to install: this file belongs to Artexis10/exomem. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Artexis10/exomem/main/.agents/skills/openspec-propose/SKILL.mdgit clone --depth 1 https://github.com/Artexis10/exomemWrote 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/artexis10/exomem/openspec-propose)<a href="https://agentmods.dev/skills/artexis10/exomem/openspec-propose"><img src="https://agentmods.dev/badge/skills/artexis10/exomem/openspec-propose/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/artexis10/exomem/openspec-propose"><img src="https://agentmods.dev/badge/skills/artexis10/exomem/openspec-propose.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.00066 | $0.03522 |
| Opus 5.5 | $0.00026 | $0.01409 |
| Sonnet 5.5 | $0.00013 | $0.00704 |
| Haiku 4.5 | $0.00007 | $0.00352 |
Grade A, and why
openspec-propose 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 13d 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 13d ago First seen · 175 lines · 66 tokens per session scan A 49187179fd7b
openspec-propose is a skill published in the GitHub repository Artexis10/exomem (10 stars, last pushed today), licensed AGPL-3.0. It adds 66 tokens to every session and 3,522 once invoked, about $0.0003 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-04.
Other skills, from other repositories
kb
Set up, evolve, or operate a hraness/kb local-first Markdown knowledge base for coding-agent memory. Use when a user asks to design KB conventions or a recurring KB ritual; search or query a KB or Obsidian vault; load or recover repository context, plans, decisions, concepts, backlinks, semantic search, or Git…
grooming
Shape ambiguous work into an agreed, executable plan. Use when the user asks to groom, scope, decompose, or prepare work before implementation.
research
Investigate an uncertain question and produce an evidence-backed decision. Use when the user asks to research, compare approaches, validate an assumption, or reduce uncertainty.
grooming-evidence
Ground work grooming in existing product evidence. Use while shaping tasks from code, documentation, tracker state, and user feedback.
research-evidence
Keep research claims traceable and proportionate to their evidence. Use while collecting, comparing, and reporting technical or product findings.
mnemonic
Search local indexed markdown knowledge bases. Use when the user asks to find notes, dig up a concept from personal docs, cross-reference ideas across wikis, or answer from indexed local files. Triggers on "look up in notes", "search my docs", "what did I write about", "find in my vault", "check my index", "retrieve…