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 foundryside-dev/warpline --skill warpline-workflowgit clone --depth 1 https://github.com/foundryside-dev/warplineWrote 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/foundryside-dev/warpline/warpline-workflow)<a href="https://agentmods.dev/skills/foundryside-dev/warpline/warpline-workflow"><img src="https://agentmods.dev/badge/skills/foundryside-dev/warpline/warpline-workflow/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/foundryside-dev/warpline/warpline-workflow"><img src="https://agentmods.dev/badge/skills/foundryside-dev/warpline/warpline-workflow.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.00109 | $0.00876 |
| Opus 5.5 | $0.00044 | $0.00350 |
| Sonnet 5.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 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.
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.
- 1mo ago 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 2mo ago), licensed MIT. It adds 109 tokens to every session and 876 once invoked, about $0.0004 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-08-31.
Other skills, from other repositories
sync-bridge
Reviews and guides Chromium Sync Model API (DataTypeSyncBridge) implementations, including DataTypeStore persistence and forwards/backwards compatibility for sync specifics. Use when implementing or reviewing a DataTypeSyncBridge subclass, DataTypeStore usage, sync metadata persistence, conflict resolution, or…
sync-model-processor
Reviews changes to Chromium Sync model internals in components/sync/model/, including ClientTagBasedDataTypeProcessor, ClientTagBasedRemoteUpdateHandler, ProcessorEntity, ProcessorEntityMetadata, and ProcessorEntityTracker. Use when modifying or reviewing processor state transitions, entity metadata tracking, conflict…
adversarial-reviewer
Stress-test a code change for concrete correctness defects, unsafe assumptions, and failure modes. Use when the user explicitly asks for an adversarial review, a deep bug hunt, or to tear a change apart, or to check your own change before submitting it. Do not use for ordinary review, style feedback, or general…
gsd-ns-review
Invoke this Pi skill with /skill:gsd-ns-review.
gitnexus
A code-graph analysis add-on for examining an existing codebase, including symbols, call paths, execution flows, and effects across repositories. It can query GitNexus through its command-line or MCP interfaces.
issue
Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance criteria, then runs the…