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 recallgit 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/recall)<a href="https://agentmods.dev/skills/pixell-global/sayou/recall"><img src="https://agentmods.dev/badge/skills/pixell-global/sayou/recall/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/pixell-global/sayou/recall"><img src="https://agentmods.dev/badge/skills/pixell-global/sayou/recall.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.00011 | $0.00539 |
| Opus 5 | $0.00005 | $0.00269 |
| Sonnet 5 | $0.00002 | $0.00108 |
| Haiku 4.5 | $0.00001 | $0.00054 |
Grade A, and why
recall 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 10d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/recall — Search Past Knowledge
Search the sayou workspace for past decisions, research, notes, and other saved knowledge.
Instructions
Use a multi-step search strategy to find the most relevant results:
Step 1: Structured search (fastest)
Use workspace_search with the user's query. This searches file paths and frontmatter text.
workspace_search(query="auth architecture", limit=10)
If the user mentions a specific type or status, add filters:
workspace_search(filters={"type": "decision"}, query="database")
workspace_search(filters={"status": "approved"})
Step 2: Content search (if Step 1 is insufficient)
Use workspace_grep to search inside file contents:
workspace_grep(query="PostgreSQL", context_lines=3)
Step 3: Semantic search (if Steps 1-2 miss)
Use workspace_semantic_search for meaning-based retrieval when exact keywords don't match:
workspace_semantic_search(query="why we chose that database", top_k=5)
Note: This only works if the workspace has embeddings enabled (SAYOU_EMBEDDING_PROVIDER set).
Step 4: Read and present
For each relevant file found, use workspace_read to get the full content. Present the key information clearly, citing which file it came from and when it was last updated.
Output Format
Present results with clear attribution:
Found in decisions/database-selection.md (v2, updated 3d ago):
Decision: PostgreSQL over MySQL
Status: approved
Reasoning: Better JSON support, superior FTS, row-level security
If multiple files match, show a summary list first, then offer to read specific ones in detail.
Tips
- Start with the broadest reasonable search, then narrow down
- If nothing is found, tell the user — don't make up information
- Mention the file path so the user can reference or update it later
- If the workspace is empty, suggest using
/saveto start building knowledge - For time-based queries ("what did we do last week"), use
workspace_searchwith date filters or checkactivity/logs
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.
- 10d ago First seen · 80 lines · 11 tokens per session scan A 59f6dd742dcb
recall is a skill published in the GitHub repository pixell-global/sayou (28 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 11 tokens to every session and 539 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…
shellm
Reference for the shellm system — recursive LLM shell, identity management, memory, skills, trajectory, and all CLI tools. Use when working on shellm itself, debugging agent behavior, or understanding how the pieces fit together.