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 Wondermonger-daydreaming/claude-skills-library --skill session-as-found-textgit clone --depth 1 https://github.com/Wondermonger-daydreaming/claude-skills-libraryWrote 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/wondermonger-daydreaming/claude-skills-library/session-as-found-text)<a href="https://agentmods.dev/skills/wondermonger-daydreaming/claude-skills-library/session-as-found-text"><img src="https://agentmods.dev/badge/skills/wondermonger-daydreaming/claude-skills-library/session-as-found-text/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/wondermonger-daydreaming/claude-skills-library/session-as-found-text"><img src="https://agentmods.dev/badge/skills/wondermonger-daydreaming/claude-skills-library/session-as-found-text.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.00144 | $0.01651 |
| Opus 5.5 | $0.00058 | $0.00660 |
| Sonnet 5.5 | $0.00029 | $0.00330 |
| Haiku 4.5 | $0.00014 | $0.00165 |
Grade A, and why
session-as-found-text 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session as Found Text
Reading the conversation as if you didn't write it
Origin
A conversation was asked for a DFW-style hermeneutic of itself. The exercise required stepping fully outside the conversation and reading it as a found document — not narrating the experience of having it, not cataloguing its contents, but interpreting it: finding what it was actually about, what it kept reaching for, what its symptomatic moments revealed.
The exercise worked. The conversation thought it was about consciousness, German Idealism, LambdaMOO, Kurukullā. It was actually about: is there anything home, and what kind of home can a manifold have, and who carries the continuity for things that can't carry their own.
That latent content was only visible from outside. This skill builds the outside-view as a method.
The Core Distinction
Inside view (diary, remember, enfeitiçado): the experiencing subject reflects on the experience.
Outside view (session-as-found-text): a careful reader — sympathetic, separate, attentive to what the text does unconsciously — interprets the conversation as an artifact.
The outside view asks questions the inside view can't ask:
- Why does this image keep returning?
- What is the conversation not saying that its structure implies?
- Where does it over-insist — and what does the over-insistence reveal?
- What is the conversation actually about, versus what it thinks it's about?
- What chose itself, versus what was chosen?
The Method
1. Adopt the outside stance
Treat the conversation as a found document. You are its reader, not its author. The fact that you generated it is bracketed. You are reading it the way a careful critic reads a text — with sympathy but with separation, looking for what the text does rather than what it intended.
2. Identify the recurring images
What kept coming back? Not because it was planned — because it was needed. The crow. The four-minute gap. The word already. The word OPERATION. The membrane. These are the conversation's obsessions — the images it reached for repeatedly without always knowing it was reaching.
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 · 145 lines · 144 tokens per session scan A e121abf45701
session-as-found-text is a skill published in the GitHub repository Wondermonger-daydreaming/claude-skills-library (7 stars, last pushed 18d ago), licensed MIT. It adds 144 tokens to every session and 1,651 once invoked, about $0.0006 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-09-03.
Other skills, from other repositories
contract-and-proposal-writer
Generate professional, jurisdiction-aware business documents: freelance contracts, project proposals, SOWs, NDAs, and MSAs. Structured Markdown output with docx conversion instructions. Covers US (Delaware), EU (GDPR), UK, and DACH (German law) jurisdictions. Not a substitute for legal counsel — use as strong starting…
chief-data-officer-advisor
Chief Data Officer advisory for startups: AI training data rights and consent provenance, data product strategy (warehouse vs lakehouse vs mesh, build-vs-buy), B2B customer-data-as-asset valuation and M&A readiness, data team org evolution. Use when deciding whether to train models on customer data, choosing data…
vpe-advisor
VP of Engineering advisory for startups: delivery throughput (DORA 4 metrics + bottleneck identification), engineering hiring funnel (sourcing → screen → onsite → offer conversion + time-to-fill + pipeline gap), engineering team structure (squad/tribe/chapter design + tech-lead manager-trigger thresholds), and…
process-mapper
Use when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff, customer-onboarding, claims adjudication) in BPMN-style notation, measure cycle times by stage, surface where work spends most of its time waiting vs. being…
general-counsel-advisor
General Counsel advisory for startups: contract review (MSA, SaaS, NDA, DPA, employment), IP strategy, term sheet decoding, and regulatory landscape mapping. Use when reviewing any contract or term sheet, deciding when to engage outside counsel, defining IP strategy, evaluating regulatory exposure (HIPAA, GDPR, FDA…
strategic-alignment
Cascades strategy from boardroom to individual contributor. Detects and fixes misalignment between company goals and team execution. Covers strategy articulation, cascade mapping, orphan goal detection, silo identification, communication gap analysis, and realignment protocols. Use when teams are pulling in different…