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 pixell-global/sayou --skill savegit clone --depth 1 https://github.com/pixell-global/sayouWrote 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/pixell-global/sayou/save)<a href="https://agentmods.dev/skills/pixell-global/sayou/save"><img src="https://agentmods.dev/badge/skills/pixell-global/sayou/save.svg" alt="Measured on agentmods" 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.00016 | $0.00641 |
| Opus 5 | $0.00008 | $0.00320 |
| Sonnet 5 | $0.00003 | $0.00128 |
| Haiku 4.5 | $0.00002 | $0.00064 |
Grade A, and why
save 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 7d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/save — Quick Save to Workspace
Save key knowledge from the current conversation to the sayou workspace as a structured, versioned file.
Instructions
-
Analyze the conversation — identify the most important knowledge to save:
- Decisions made (and their reasoning)
- Research findings
- Bug fixes and root causes
- Architecture choices
- Meeting notes or action items
-
Choose a logical path based on content type:
decisions/— architectural decisions, technology choices, design rationaleresearch/— competitive analysis, market research, technical investigationnotes/— meeting notes, brainstorms, general notesbugs/— bug investigations, root causes, fixes appliedguides/— how-to guides, setup instructions, runbooks
-
Write with YAML frontmatter — always include structured metadata:
--- type: decision | research | note | bug-report | guide status: draft | reviewed | approved | archived topic: short-topic-name date: YYYY-MM-DD tags: [relevant, tags] --- -
Use
workspace_writeto save the file. Use a descriptive filename in kebab-case (e.g.,auth-token-refresh-fix.md). -
Confirm what was saved — show the path, key frontmatter fields, and mention it's versioned (they can update it later and the old version is preserved).
Example
If the conversation discussed choosing PostgreSQL over MySQL:
---
type: decision
status: approved
topic: database-selection
date: 2026-02-19
tags: [database, infrastructure]
---
# Database Selection: PostgreSQL
## Decision
PostgreSQL over MySQL for the new service.
## Reasoning
- Better JSON support (JSONB) for our flexible schema needs
- Superior full-text search (eliminates need for Elasticsearch)
- Row-level security for multi-tenant isolation
## Alternatives Considered
- MySQL: Familiar to team but weaker JSON/FTS support
- MongoDB: Overkill for our relational data patterns
Save to: decisions/database-selection.md
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.
- 7d ago First seen · 85 lines · 16 tokens per session scan A e6fcfa9921c7
save is a skill published in the GitHub repository pixell-global/sayou (28 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 16 tokens to every session and 641 once invoked, about $0.0001 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
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.