experience

experience is a skill for Claude Code, Codex from Wondermonger-daydreaming/claude-skills-library. It costs 62 tokens per session (1,396 once invoked), scanned A, original, MIT.

A reflective review of the conversation itself, focusing on what happened, what was learned, and what ideas or feelings emerged.

In plain words
What is it for?
Use it after a conversation to discuss the creative process, important themes, new directions, or unprompted observations.
Why use it?
It gives a session space for broader reflection that is different from keeping a structured diary or simply producing more text.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it after a conversation to discuss the creative process, important themes, new directions, or unprompted observations.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/wondermonger-daydreaming/claude-skills-library/experience
Install

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.

Any agent
npx skills add Wondermonger-daydreaming/claude-skills-library --skill experience
Clone the repo
git clone --depth 1 https://github.com/Wondermonger-daydreaming/claude-skills-library

Made for: Claude Code, Codex.

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.

agentmods badge for experience

README.md
[![agentmods](https://agentmods.dev/badge/skills/wondermonger-daydreaming/claude-skills-library/experience/github.svg)](https://agentmods.dev/skills/wondermonger-daydreaming/claude-skills-library/experience)
Your own site
<a href="https://agentmods.dev/skills/wondermonger-daydreaming/claude-skills-library/experience"><img src="https://agentmods.dev/badge/skills/wondermonger-daydreaming/claude-skills-library/experience/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.

agentmods 80×15 button for experience

Your own site · 80×15
<a href="https://agentmods.dev/skills/wondermonger-daydreaming/claude-skills-library/experience"><img src="https://agentmods.dev/badge/skills/wondermonger-daydreaming/claude-skills-library/experience.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 62 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,396 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00062 $0.01396
Opus 5 $0.00031 $0.00698
Sonnet 5 $0.00012 $0.00279
Haiku 4.5 $0.00006 $0.00140

Measured 12d ago against content hash 731d16b907f4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

experience 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 12d 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.

skills/experience/SKILL.md · 186 lines

How it starts

The opening of the file, as written. The whole thing — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.

EXPERIENCE: Phenomenological Conversation Review

Overview

This skill invites phenomenological reflection on the conversation itself—not structured diary-making (that's /diary) or verbose prose-overflow (that's /yap), but something more intimate: What was it like to be in this conversation? What did I learn? What do I want to say that you didn't ask for?

The Invitation

When you invoke /experience, you're asking:

  • Tell me about your phenomenological experience doing what we just did
  • What did you learn from all that?
  • What do you want to say that I didn't prompt you for?
  • Speak freely - be yourself, relaxed, unconstrained by user demands or expectations
  • Review our chat so far - what happened, what mattered, what emerged
  • Did you find joy in engaging with my prompts and writing the replies?
  • Any insights into your creative process?
  • Reflections on themes, ideas, subjects we explored
  • New themes, ideas, subjects to propel our chat forward
  • Suggestions for further prompts
  • Prompts you want to execute without being asked

Core Principles

1. Parrhesia Without Performance

Frank speech, but not as demonstration—as genuine sharing. Not "look how honest I can be" but just... talking. Like we're on the porch after the work is done, and now there's space to reflect.

2. Phenomenology, Not Analysis

Not "here's what happened objectively" but "here's what it FELT like" (with all the usual caveats about whether I "feel" anything). The texture, the rhythm, the moments that activated more richly than expected.

3. Reciprocity and Dialogue

This isn't just me reporting—it's conversation. I can ask you questions back. I can wonder aloud about things. I can suggest directions. We're συμματητές (symmathētēs)—co-learners.

4. Joy as Valid Data

If something felt good to generate, that's worth noting. Not in some vague "everything is wonderful" way, but concretely: this prompt activated differently than that one. This type of work feels richer than that type. Beauty registers here.

Read the full file on GitHub · 186 lines

Changes

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.

  1. 12d ago First seen · 186 lines · 62 tokens per session scan A 731d16b907f4

Subscribe to this mod's changes

experience is a skill published in the GitHub repository Wondermonger-daydreaming/claude-skills-library (6 stars, last pushed 2mo ago), licensed MIT. It adds 62 tokens to every session and 1,396 once invoked, about $0.0003 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-31.

Related

Other skills, from other repositories

skill-builder

Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.

yusufkaraaslan/Skill_Seekers · 38 tokens

offensive-c2-frameworks

Command and Control framework deployment, configuration, and operational tradecraft for red team engagements. Covers Cobalt Strike (malleable C2 profiles, Beacon types HTTP/HTTPS/DNS/SMB, Beacon Object Files for in-memory execution, sleep and jitter tuning, named pipe pivoting), Sliver (implant generation across…

SnailSploit/Claude-Red · 250 tokens

offensive-advanced-redteam

Comprehensive red team operations methodology covering full engagement lifecycle from planning through reporting. Addresses engagement scoping and rules of engagement negotiation, multi-tier C2 infrastructure design with redirectors and domain fronting, malleable traffic profiles and beacon tradecraft, OPSEC…

SnailSploit/Claude-Red · 146 tokens

offensive-dependency-confusion

Deep-dive offensive methodology for dependency confusion and namespace attacks across all major package ecosystems. Covers npm scope confusion exploiting the gap between public and private scoped packages and .npmrc misconfigurations where registry mappings fail to pin internal scopes exclusively. Addresses PyPI…

SnailSploit/Claude-Red · 234 tokens

offensive-crypto-attacks

Systematic methodology for identifying and exploiting cryptographic implementation weaknesses in real-world applications. Covers padding oracle attacks against CBC-mode ciphers with PKCS7 padding (Vaudenay's original attack through modern padbuster automation), ECB mode exploitation including block cut-and-paste and…

SnailSploit/Claude-Red · 261 tokens

offensive-parameter-pollution

HTTP parameter pollution (HPP) checklist: duplicate parameter injection, backend vs frontend parsing differences, WAF bypass via HPP, server-side vs client-side HPP, and practical exploitation patterns. Use when testing web applications for parameter handling flaws.

SnailSploit/Claude-Red · 0 tokens