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 ulises-jeremias/agent-toolkit --skill workspace-knowledge-syncgit clone --depth 1 https://github.com/ulises-jeremias/agent-toolkitWrote 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/ulises-jeremias/agent-toolkit/workspace-knowledge-sync)<a href="https://agentmods.dev/skills/ulises-jeremias/agent-toolkit/workspace-knowledge-sync"><img src="https://agentmods.dev/badge/skills/ulises-jeremias/agent-toolkit/workspace-knowledge-sync/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/ulises-jeremias/agent-toolkit/workspace-knowledge-sync"><img src="https://agentmods.dev/badge/skills/ulises-jeremias/agent-toolkit/workspace-knowledge-sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00064 | $0.01747 |
| Opus 5.5 | $0.00026 | $0.00699 |
| Sonnet 5.5 | $0.00013 | $0.00349 |
| Haiku 4.5 | $0.00006 | $0.00175 |
Grade A, and why
workspace-knowledge-sync 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 — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workspace Knowledge Sync
Automatically syncs valuable discoveries, patterns, and decisions to the agentic-harness knowledge base and durable AGENTS.md learned facts.
Purpose
The orchestrator session accumulates knowledge through work. This skill ensures that valuable discoveries don't get lost and are available for future sessions — both in the workspace knowledge base (knowledge/) and as durable learned facts in AGENTS.md.
Inspired by cursor/plugins continual-learning (without hooks — no transcript mining or stop hook).
Trigger Points (Automatic)
The platform-engineer (archived tech-assistant — now inline references/WORKSTATION_OPS.md) will invoke this skill automatically when:
| Situation | What to Sync | Target |
|---|---|---|
| Discovery of new skill/tool | Skill name, purpose, usage pattern | knowledge/skills/discovered.md |
| New process pattern | Process steps, roles, tools | knowledge/processes/general.md |
| Key decision made | Decision, rationale, outcome | knowledge/learnings/general.md |
| Pending follow-up | Task description, context | knowledge/todos/pending.md |
| User teaches something | Information, preference | Relevant knowledge file |
| Recurring user preference / correction | Plain bullet, durable preference | AGENTS.md → ## Learned User Preferences |
| Stable workspace fact | Plain bullet, durable fact | AGENTS.md → ## Learned Workspace Facts |
How It Works
Knowledge base (agent-toolkit memory)
The skill uses the stable agent-toolkit memory API with --from-skill for origin tracking (harness alias: assistant-memory / bin/assistant-memory):
# Search before adding
agent-toolkit memory search "<query>"
# Add a learning (with origin tracking)
agent-toolkit memory add --type learning --from-skill knowledge-sync "Pattern: <description>"
# Add a skill (with tags)
agent-toolkit memory add --type skill --from-skill knowledge-sync --tags jira,workflow "New skill: <name>"
# Add a pending todo
agent-toolkit memory add --type todo --from-skill knowledge-sync "<description>"
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 · 227 lines · 64 tokens per session scan A 69de4f8a32bf
workspace-knowledge-sync is a skill published in the GitHub repository ulises-jeremias/agent-toolkit (19 stars, last pushed yesterday), licensed MIT. It adds 64 tokens to every session and 1,747 once invoked, about $0.0003 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-04.
Other skills, from other repositories
chatcrystal-task-writeback
Write reusable ChatCrystal task memories after substantive work completes. Use when implementation or debugging produced a durable fix, pitfall, pattern, or decision worth preserving, and when the environment can either persist it through writetaskmemory or emit a structured memory candidate for later save.
chatcrystal-debug-recall
Recall ChatCrystal memories for debugging tasks involving failing tests, compiler errors, runtime exceptions, dependency issues, environment breakage, or performance regressions. Use when historical root causes, fixes, or pitfalls may accelerate diagnosis before proposing a fix.
chatcrystal-task-recall
Recall project-first and global-supplement ChatCrystal memories before substantive implementation, refactoring, migration, configuration, investigation, or optimization work. Use when the task is non-trivial, has repository or project context, and prior fixes, decisions, pitfalls, or reusable patterns may change the…
audit-history
Use when reviewing past agent sessions, auditing memory health, identifying repeated corrections or friction, cleaning up stale memories, proposing new skills and rules from usage patterns, or identifying mechanical improvements (testing, linting, static analysis, tooling) that could improve outcomes.
teach
Updates the project knowledge base (.vibeflow/) with corrections, new conventions, architectural decisions, or new patterns based on natural language feedback. Also imports patterns from external repos through the --from option. Edits are placed outside auto-generated markers to survive incremental analyze runs. Use…
vibeflow-teach
Updates .vibeflow/ with corrections, new conventions, architectural decisions, or new patterns from natural language feedback. Also imports from external repos through the --from option. Use to keep .vibeflow/ accurate as the project evolves.