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 agentmods add skills/lookatitude/guild/learnnpx skills add lookatitude/guild --skill learngit clone --depth 1 https://github.com/lookatitude/guildWhat 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 | $0.00284 | $0.06496 |
| Opus 5 | $0.00142 | $0.03248 |
| Sonnet 5 | $0.00057 | $0.01299 |
| Haiku 4.5 | $0.00028 | $0.00650 |
Grade A, and why
guild-learn 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 2d 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 — 450 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to use it
Use when /guild:learn is called with no sub-verb — the "learn this
project completely" intent. Implements the §"Smart /guild:learn Behavior"
contract from learn-knowledge-run-convergence.md (SC-A).
Explicit sub-verbs (map, graph, onboard, diff, explain) bypass this
skill entirely and route directly to their specialist skill. This skill owns
only the no-arg full-learn path.
When not to use it
Not for any explicit sub-verb invocation (those go directly to guild:learn-map
/ guild:learn-graph / guild:learn-onboard / guild:learn-diff /
guild:learn-explain). Not for querying an existing graph (kg-query /
guild:wiki-query). Not for a single-source ingest (guild:wiki-ingest).
Not as an alternative to guild:learn-harvest (which is for phase/run
artifact extraction, not code).
Required inputs
- The repo root (resolved worktree-safe;
lib/paths.tsredirects ephemeral worktrees to the main root). - Optional:
--dry-runflag → print the fan-out plan, write nothing. - Optional:
--cwd <path>to override the detected root. - Config:
readWorkspaceKnowledgeConfig(root)from B2'splugin/scripts/lib/run-lifecycle.tsexposeslearn_fanout: "auto" | "plan-only"(B2 handoff §3).
Detection and confirmation (never silent)
Implements the §"Detection" contract (brief §170-177, spec SC-A):
Classify the target into exactly one of:
regular_project has .guild/ or .git/, no child repos at depth-1
workspace ≥1 immediate children with .git/ or .guild/ (detected
by workspace/detect.ts)
existing_guild_project regular project with a populated .guild/wiki/
new_or_sparse_project .guild/ absent or empty; ≤5 tracked files
mixed_or_uncertain children found but ambiguous (some have .git/, some have
.guild/, workspace/detect.ts reports "uncertain")
Detection script: npx tsx ${GUILD_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT:-$HOME/.local/share/guild/dist/claude-code}}/scripts/workspace/detect.ts --cwd <root> (depth-1
fixed, no knob). For mixed_or_uncertain surface one targeted question before
proceeding; never silent-proceed on uncertainty. Mirror the bare /guild:guild
§5.1 confirm contract: show detection → ask proceed / pick / explain.
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.
- 2d ago First seen · 450 lines · 284 tokens per session scan A 9e4fcb59bbeb
guild-learn is a skill published in the GitHub repository lookatitude/guild (7 stars, last pushed 2d ago), licensed MIT. It adds 284 tokens to every session and 6,496 once invoked, about $0.0014 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.