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 denn-gubsky/loomcycle --skill edge-linkinggit clone --depth 1 https://github.com/denn-gubsky/loomcycleWrote 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/denn-gubsky/loomcycle/edge-linking)<a href="https://agentmods.dev/skills/denn-gubsky/loomcycle/edge-linking"><img src="https://agentmods.dev/badge/skills/denn-gubsky/loomcycle/edge-linking/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/denn-gubsky/loomcycle/edge-linking"><img src="https://agentmods.dev/badge/skills/denn-gubsky/loomcycle/edge-linking.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.00026 | $0.00329 |
| Opus 5 | $0.00013 | $0.00164 |
| Sonnet 5 | $0.00005 | $0.00066 |
| Haiku 4.5 | $0.00003 | $0.00033 |
Grade A, and why
doc/edge-linking 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 9d 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.
What it actually says
Edge linking
Chunks form a tree by parent_id, but they also carry a free-form graph of
typed edges (link_chunks) — "this publication promotes that blog post", "this
task targets that requirement". Use edges for cross-cutting relations that the
parent/child hierarchy can't express.
Method
- Resolve both endpoints first with
query_chunks/get_chunk— both chunks must already exist (an edge to a missing chunk is refused). Cross-document edges are allowed as long as both chunks are in this scope. - Pick a clear
kindverb the operator will recognize:references,promotes,targets,depends_on,supersedes. Reuse existing kinds in the document rather than inventing near-duplicates. - Link:
Document op=link_chunks from_id=<a> to_id=<b> kind="references"(idempotent — re-linking the same triple is a no-op). - Remove a stale edge with
op=unlink_chunks from_id=<a> to_id=<b> kind="…".
Notes
- Edges are directional (
from → to). State the direction back to the operator. - Don't use an edge where a parent/child move is what's meant — see the doc/restructuring skill.
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.
- 9d ago First seen · 30 lines · 26 tokens per session scan A 9e7dd69ea9c9
doc/edge-linking is a skill published in the GitHub repository denn-gubsky/loomcycle (13 stars, last pushed today), licensed Apache-2.0. It adds 26 tokens to every session and 329 once invoked, about $0.0001 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-30.
Other skills, from other repositories
pdf-processing
Extract text and tables from PDF files, fill forms, merge documents. Use when working with PDF files or when the user mentions PDFs, forms, or document extraction.
co-mail-and-drive
Read and send mail from the user's own Gmail or Outlook account, safely stage Gmail draft attachments, send from the agent's own address, manage Outlook contacts, and work with Google Drive files — with co gmail, co outlook, co email, and co gdrive. Use when the user asks about their inbox, an email or draft they want…
weknora-shared
Use when driving a WeKnora RAG server through the weknora CLI as an agent — authenticating, managing knowledge bases / documents / sessions / agents, running search or chat, or interpreting the CLI's JSON envelopes and exit codes. Read this before any other weknora- skill.
weknora-rag-search
Use when retrieving from or asking questions against a WeKnora knowledge base via the weknora CLI — and especially when unsure whether to use chat, session ask, or search chunks for a given goal.
upload-artifact
Upload a file as a ClosedLoop document (PRD, implementation plan, feature, or template). Reads file content and uploads via MCP without consuming conversation context. Also supports creating new versions of existing documents. Triggers on: "upload artifact", "upload PRD", "upload implementation plan", "upload…
extract-plan-md
Sync plan.md with plan.json content. MUST be used after ANY edit to plan.json to keep plan.md in sync. Triggers: After editing plan.json with Edit tool (REQUIRED - always sync after edits) User asks to "sync plan.md", "update plan.md", "extract the md from a plan" Converting plan.json to markdown or viewing plan as…