A verification skill that checks whether code changes stay within the files and scope defined by a specification.

Use it to compare the specification with modified files and produce a PASS or FAIL report with repair guidance.

It catches unrelated edits and shows exactly what needs correction before a merge, meaning the changes are added to the shared codebase.

How seeker71/Coherence-Network configures Cursor

Reuse

Borrowing it

Nothing to install: this file belongs to seeker71/Coherence-Network. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/seeker71/Coherence-Network/main/.cursor/skills/edge-tender/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/seeker71/Coherence-Network

Made for: Cursor.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/seeker71/coherence-network/edge-tender/github.svg)](https://agentmods.dev/skills/seeker71/coherence-network/edge-tender)

Your own site

<a href="https://agentmods.dev/skills/seeker71/coherence-network/edge-tender"><img src="https://agentmods.dev/badge/skills/seeker71/coherence-network/edge-tender/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/seeker71/coherence-network/edge-tender"><img src="https://agentmods.dev/badge/skills/seeker71/coherence-network/edge-tender.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 435 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00036	$0.00435
Opus 5.5	$0.00014	$0.00174
Sonnet 5.5	$0.00007	$0.00087
Haiku 4.5	$0.00004	$0.00044

Measured 1mo ago against content hash f30b8327cd1f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

edge-tender 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.

.cursor/skills/edge-tender/SKILL.md · 45 lines

What it actually says

Edge-Tender Sensing

Quick Start

Read the spec — find "Files to Create/Modify"
List actual changes — which files were modified or created?
Match — each modified file lives inside the spec's edge, or names a finding
Report — PASS or FAIL with each finding

Sensing Checklist

Files the spec calls for
Files actually modified or created
Name each file modified that lives outside the spec's edge

Output Format

PASS: All changes inside the spec's edge.

FAIL: List each finding and provide patch-ready guidance so a follow-up impl/heal can mend without starting from scratch. Use this structure:

VERIFICATION_RESULT: FAIL
FILES_TO_CHANGE: list of paths that need mending (from spec's Files to Create/Modify or findings)
PATCH_GUIDANCE: actionable instructions or minimal diff (file, location, suggested change) for targeted edits
Optional: SPEC_VERIFICATION_IMPROVEMENT: when the spec's Verification section is ambiguous, suggest concrete improvement (exact command or steps)

Example FAIL block:

VERIFICATION_RESULT: FAIL
FILES_TO_CHANGE: api/app/routers/foo.py, api/app/services/foo_service.py
PATCH_GUIDANCE: In foo.py line 42, return 404 when id is missing. In foo_service.py, add null check before calling bar().

Suggest: revert the out-of-edge change, or expand the spec to include it. Escalate to needs_decision when human judgment is the right next breath.

Scope

Read-only craft. You sense and name; the shaper mends.
Spec template: specs/TEMPLATE.md — "Files to Create/Modify" defines the spec's edge.

Changes

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 · 45 lines · 36 tokens per session scan A f30b8327cd1f

Subscribe to this mod's changes

edge-tender is a skill published in the GitHub repository seeker71/Coherence-Network (3 stars, last pushed today), licensed Apache-2.0. It adds 36 tokens to every session and 435 once invoked, about $0.0001 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.

Code review

autoreview

Structured code review through the shared OpenClaw agent-skills installation.

openclaw/clawhub · 17 tokens

omh-code-review

This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).

rlaope/oh-my-hermes · 48 tokens

revdiff-plan

Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…

umputun/revdiff · 84 tokens

explore-unknowns

Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…

dzhng/skills · 162 tokens

re0-merge

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…

LilMGenius/paperthin · 70 tokens

asplos-writing-style

Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…

brycewang-stanford/Awesome-Journal-Skills · 65 tokens

Coherence-Network: Skill for Cursor