Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/DSmmartin/skills_talk_agent_camp_2026npx agentmods add skills/dsmmartin/skills_talk_agent_camp_2026/03_fully_guidedWrote 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/dsmmartin/skills_talk_agent_camp_2026/03_fully_guided)<a href="https://agentmods.dev/skills/dsmmartin/skills_talk_agent_camp_2026/03_fully_guided"><img src="https://agentmods.dev/badge/skills/dsmmartin/skills_talk_agent_camp_2026/03_fully_guided/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/dsmmartin/skills_talk_agent_camp_2026/03_fully_guided"><img src="https://agentmods.dev/badge/skills/dsmmartin/skills_talk_agent_camp_2026/03_fully_guided.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.00065 | $0.01068 |
| Opus 5 | $0.00032 | $0.00534 |
| Sonnet 5 | $0.00013 | $0.00214 |
| Haiku 4.5 | $0.00006 | $0.00107 |
Grade A, and why
schema-sync-fully-guided 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 11d 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Schema Sync — Fully Guided
Read dev_tools/README.md and dev_tools/skill_examples/03_fully_guided/references/schema-layers.md
before starting. They contain field-level detail about what each layer holds and what to change.
One-command fix
If the migration matches the standard merged → merged_at rename pattern, the full procedure
is automated:
# Preview what will change (nothing is written)
uv run python dev_tools/schema_sync.py --table github_events --dry-run
# Apply all four patches
uv run python dev_tools/schema_sync.py --table github_events
# Confirm no drift
uv run python scripts/validate_schema.py
A SchemaSyncReport is printed listing every change made across all four layers.
Step-by-step procedure (for non-standard migrations)
Use this when the one-command fix does not cover the migration, or when you need to apply patches selectively.
Pre-check — confirm drift exists
uv run python scripts/validate_schema.py
If "No drift" is reported, the system is already in sync. Stop here.
Step 1 — Introspect live ClickHouse schema
uv run python dev_tools/scripts/clickhouse_introspect.py --table github_events
Note every column that is new, removed, or type-changed compared to the YAML contract.
See references/schema-layers.md for the expected post-migration schema.
Step 2 — Patch YAML contract
# Preview
uv run python dev_tools/scripts/yaml_patch.py --table github_events --dry-run
# Apply
uv run python dev_tools/scripts/yaml_patch.py --table github_events
If patching manually: edit agentic_system/schema/github_events.yaml.
- Add the new column entry (name, type, description).
- Update the description of any renamed or type-changed column to document post-migration semantics.
- Do NOT remove columns that still exist in the DB (even if zeroed out).
Step 3 — Patch ChromaDB RAG chunks
# Preview
uv run python dev_tools/scripts/chroma_patch.py --dry-run
# Apply
uv run python dev_tools/scripts/chroma_patch.py
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 141 lines · 65 tokens per session scan A a08e83cbe61b
schema-sync-fully-guided is a skill published in the GitHub repository DSmmartin/skills_talk_agent_camp_2026 (9 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 65 tokens to every session and 1,068 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.
Other skills, from other repositories
qdrant
Vector search engine for production RAG systems.
chroma
Embedding database for RAG and semantic search.
pinecone
Managed vector DB for production RAG and search.
embeddings
Vector embeddings with HNSW indexing, sql.js persistence, and hyperbolic support. 75x faster with agentic-flow integration. Use when: semantic search, pattern matching, similarity queries, knowledge retrieval. Skip when: exact text matching, simple lookups, no semantic understanding needed.
similarity-search-patterns
Implement efficient similarity search with vector databases. Use when building semantic search, implementing nearest neighbor queries, or optimizing retrieval performance.
pgvector-semantic-search
Use this skill for setting up vector similarity search with pgvector for AI/ML embeddings, RAG applications, or semantic search. Trigger when user asks to: Store or search vector embeddings in PostgreSQL Set up semantic search, similarity search, or nearest neighbor search Create HNSW or IVFFlat indexes for vectors…