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/foundryside-dev/warpline/warpline-workflownpx skills add foundryside-dev/warpline --skill warpline-workflowgit clone --depth 1 https://github.com/foundryside-dev/warplineWhat 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.00109 | $0.00876 |
| Opus 5 | $0.00055 | $0.00438 |
| Sonnet 5 | $0.00022 | $0.00175 |
| Haiku 4.5 | $0.00011 | $0.00088 |
Grade A, and why
warpline-workflow 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 yesterday.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- warpline-workflow — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Warpline Workflow
warpline is the federation's temporal / change-impact authority — "if I touch X, what breaks, and what must I re-verify?". It owns temporal change facts and dated edge snapshots; it does NOT own current structure (loomweave), work state (filigree), trust policy (wardline), or governance (legis).
The tools (endorsed name / short shim — identical schema+data)
warpline_change_list/changed— changed entities for a repo + rev range. Returnsnext_actionspointing at reverify/impact. Call this first.warpline_impact_radius_get/blast_radius— downstream affected set over the dated snapshot. Carries mandatorycompleteness+staleness.warpline_reverify_worklist_get/reverify— the worklist to recheck before claiming completion. The flagship.warpline_entity_timeline_get/timeline— ordered change history for one entity; reportssei_resolutiononly, never lineage.warpline_entity_churn_count_get/churn— per-entity change-event counts.warpline_edge_snapshot_capture/capture_snapshot— the only mutating tool; captures dated loomweave edges into.weft/warpline/. Run when impact/reverify reportsNO_SNAPSHOTand loomweave is available.
Typical loop
changed(rev_range, e.g.HEAD~1..HEAD) → readnext_actions.reverify(orblast_radius) with the suggested arguments.- If
completeness: NO_SNAPSHOT, runcapture_snapshot, then retry.
Reading the answer honestly
completenessisFULL | DELTA | NO_SNAPSHOT | SKIPPED;stalenessreports the snapshot commit and how far behind HEAD it is. A thin answer looks thin — never treatNO_SNAPSHOTas "nothing is affected".enrichmentis a CLOSED vocab:present/absent(peer present, no fact) /unavailable(peer unreachable). Sibling absence is explicit, never an implied clean/allowed state. warpline never gates — its facts are advisory.- Every entity carries both
locatorandsei(loomweave:eid:..., opaque). - Every response is
meta.local_only: true,peer_side_effects: [].
What ships with it
4 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.
- yesterday First seen · 65 lines · 109 tokens per session scan A f7f1be3e232b
warpline-workflow is a skill published in the GitHub repository foundryside-dev/warpline (0 stars, last pushed 21d ago), licensed MIT. It adds 109 tokens to every session and 876 once invoked, about $0.0005 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.