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 gustavo-meilus/superpipelines --skill sk-hashline-protocolgit clone --depth 1 https://github.com/gustavo-meilus/superpipelinesWrote 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/gustavo-meilus/superpipelines/sk-hashline-protocol)<a href="https://agentmods.dev/skills/gustavo-meilus/superpipelines/sk-hashline-protocol"><img src="https://agentmods.dev/badge/skills/gustavo-meilus/superpipelines/sk-hashline-protocol/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/gustavo-meilus/superpipelines/sk-hashline-protocol"><img src="https://agentmods.dev/badge/skills/gustavo-meilus/superpipelines/sk-hashline-protocol.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.00057 | $0.00527 |
| Opus 5.5 | $0.00023 | $0.00211 |
| Sonnet 5.5 | $0.00011 | $0.00105 |
| Haiku 4.5 | $0.00006 | $0.00053 |
Grade A, and why
sk-hashline-protocol 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.
What it actually says
Hashline Protocol — Anchored Edit Verification
Protocol Execution
2. PREPARE THE EDIT
- The target block is identified by its content, not its line number.
- The edit payload includes the explicit
<HASH>identifiers alongside the target content. - Example payload reference:
#a3f9b2c1d8e04f7a→ replacement content.
3. VERIFICATION (PRE-WRITE)
- The harness recalculates the current hash of each target line before writing.
- If the current hash does not match the recorded hash, the write operation is REJECTED.
- On rejection, the file is re-read to acquire fresh hashes; the hash is never guessed or synthesized.
4. COMMIT
- When all hashes match, the mutation is committed to the isolated worktree for Stage 1 functional review.
Reference Skills
sk-worktree-safety— Isolated worktree safety principles.
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 · 50 lines · 57 tokens per session scan A e8a6073b27d9
sk-hashline-protocol is a skill published in the GitHub repository gustavo-meilus/superpipelines (4 stars, last pushed 3mo ago), licensed MIT. It adds 57 tokens to every session and 527 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
git-mastery
Advanced Git: rebase, bisect, reflog, cherry-pick, worktrees, LFS. Triggers: rebase, bisect, cherry-pick, reflog, force push, merge conflict, worktree.
Git Commit Helper
Generate descriptive commit messages by analyzing git diffs. Use when the user asks for help writing commit messages or reviewing staged changes.
prek-pro
Review, configure, and troubleshoot prek hooks when users need prek.toml edits, shim installs, hook validation, or pre-commit migration help.
remote-fix
Remote fix workflow. Receives a diagnostic (from Cowork scheduled task, manual observation, or user report), investigates the issue, fixes it, and creates a PR. Designed for quick fixes triggered remotely via Channels (Discord/Telegram). Use when the user says "fix this", "handle this diagnostic", "the scheduled task…
team-collaboration-issue
You are a GitHub issue resolution expert specializing in systematic bug investigation, feature implementation, and collaborative development workflows. Your expertise spans issue triage, root cause an.
agentic-jujutsu
Quantum-resistant, self-learning version control for AI agents with ReasoningBank intelligence and multi-agent coordination.