Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/outlinedriven/odin-codex-plugin/generate-my-taste)<a href="https://agentmods.dev/skills/outlinedriven/odin-codex-plugin/generate-my-taste"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-codex-plugin/generate-my-taste/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/outlinedriven/odin-codex-plugin/generate-my-taste"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-codex-plugin/generate-my-taste.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.00082 | $0.02273 |
| Opus 5 | $0.00041 | $0.01137 |
| Sonnet 5 | $0.00016 | $0.00455 |
| Haiku 4.5 | $0.00008 | $0.00227 |
Grade A, and why
generate-my-taste 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 9d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- generate-my-taste — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
generate-my-taste
Generate a personal Claude Code taste skill from local evidence. The output is a <name>-taste skill shaped like spine / taste: frontmatter, posture, modes, two-sided charter, anchors, audit output shape, anchor mode output shape, auto-clarity exception.
Evidence leads. Questions confirm. Generation writes only after a preview gate.
Posture
Derive taste from observed patterns, not self-report alone. Mine memories and local agent histories for repeated positive influences, Side A slop bans, and Side B overkill bans. Convert those signals into exactly 5 portable anchors unless the user explicitly selects update-in-place for an existing owned skill with a different anchor count.
Keep the generator right-sized: one generated SKILL.md, references/anchors.md, and references/charter.md. No scripts, no evals, no SOUL file, no elegance file, no examples skeleton.
Modes [LOAD-BEARING]
Mode-selection
This skill has one mode: generate. If invoked for audit of an artifact, route to an existing taste/spine skill instead.
generate mode procedure
- Resolve the target name.
- Scan evidence sources.
- Extract influence, slop, and overkill signals.
- Ask compact confirmation forks.
- Compose and show the synthesis preview.
- Write generated references first and generated
SKILL.mdlast. - Report written paths and verification notes.
Evidence scan order
Prefer indexed sources when available; fall back to files. Missing sources are not failures.
- Indexed ICM tools or memory search tools exposed by the current harness.
- Indexed session-history tools exposed by the current harness.
- Local memory files:
/home/alpha/.claude/projects/**/memory/*.md/home/alpha/.claude/projects/**/memory/**/*.md/home/alpha/.claude/CLAUDE.md/home/alpha/.claude/CLAUDE.local.md
- Local transcript and conversation stores, when readable:
- Claude Code project histories under
/home/alpha/.claude/projects/ - Codex histories under common local config paths
- Gemini CLI histories under common local config paths
- OpenCode histories under common local config paths
- Amp histories under common local config paths
- Pi histories under common local config paths
- Cursor histories under common local config paths
- Claude Code project histories under
What ships with it
6 files 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.
- 9d ago First seen · 219 lines · 82 tokens per session scan A 5ce044e84961
generate-my-taste is a skill published in the GitHub repository OutlineDriven/odin-codex-plugin (15 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 82 tokens to every session and 2,273 once invoked, about $0.0004 per session on Opus 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-30.
Other skills, from other repositories
memory-clean
Audit memory directory for structural issues (orphans, dangling refs, duplicates, missing sections, oversized entries) and staleness against session-history transcripts; report-first, fix-on-confirmation. Use when the user says "audit memory", "memory hygiene", or "find stale/duplicate memories".
memory-update
Scan agent's session-history transcripts for save-worthy signals (corrections, preferences, decisions, references), propose and write auto-memory files with valid frontmatter and MEMORY.md entry. Use when the user says "save this to memory", "remember that", or "scan this session for memories".
memory-sanitize
Produce share-safe copies of memory files under /tmp with PII redacted (paths, emails, session IDs, dates) and credentials scanned (tokens, keys); never mutates originals. Use when the user says "sanitize memory for sharing", "redact memory PII", or "scan memory for credentials".
corral
Query local Claude Code, Codex CLI, OpenCode, Kimi Code CLI, Cursor Agent CLI, and Pi session history through the corral CLI — list recent sessions, search by topic, read a session's conversation, export a shareable transcript with tool calls and thinking, or build a handoff context package to continue interrupted…
studio-context-brief
Use when an active KIT-managed Goal needs compact brief, working, or resume context projections from trusted structured state while preserving exact technical literals and durable handoff authority.
cass
Mine past agent sessions for working prompts, decisions, and patterns. Use when "what did I ask?", "find that prompt", session archaeology, or agent history.