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/chennest/hline/hline-usagenpx skills add chennest/hline --skill hline-usagegit clone --depth 1 https://github.com/chennest/hlineWrote 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/chennest/hline/hline-usage)<a href="https://agentmods.dev/skills/chennest/hline/hline-usage"><img src="https://agentmods.dev/badge/skills/chennest/hline/hline-usage.svg" alt="Measured on agentmods" 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 | $0.00040 | $0.01085 |
| Opus 5 | $0.00020 | $0.00543 |
| Sonnet 5 | $0.00008 | $0.00217 |
| Haiku 4.5 | $0.00004 | $0.00109 |
Grade A, and why
hline-usage 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
hline Usage Guide for AI Agents
Overview
hline = hcat (view) + hsed (edit). Hash-anchored file operations for SSH environments. Zero dependencies, single binary.
- hcat — Read files with hash anchors on each line
- hsed — Edit files via those anchors (replace / append / prepend)
Repo: https://github.com/chennest/hline | Install: see README
When to Use
- SSH access to a remote server with
hcat/hsedinstalled - Need to read/edit files unreachable by native agent tools
sedis too fragile for the edit
Do NOT use for: local files (use native tools), binary files, non-UTF-8 content.
How It Works
Each line gets a 2-char hash anchor based on its content (not position). Hash binds to content only — insertions/deletions elsewhere won't invalidate anchors on untouched lines.
Format: {line_number}#{hash}|{content}
11#XJ| function hello() {
12#MB| return "world";
13#QR| }
hcat — View Files
hcat /path/to/file # Full file
hcat /path/to/file 5-10 # Lines 5-10
hcat /path/to/file 5 # Line 5 to EOF
hcat /path/to/file 5 +10 # Line 5 + next 10 lines
hcat /path/to/file -A 3 5 # Line 5 + 3 after (space required)
hcat /path/to/file -B 2 -A 3 5 # Line 5 + 2 before + 3 after
⚠️ -A/-B require space: -A 3 ✓, -A3 ✗
hsed — Edit Files
Usage: hsed <file> <operation> <anchor(s)> << 'EOF' then content, then EOF.
# Replace single line
hsed /path/to/file replace 11#XJ << 'EOF'
new content
EOF
# Replace range (start anchor, end anchor)
hsed /path/to/file replace 11#XJ 13#QR << 'EOF'
multi-line replacement
EOF
# Delete range (empty content)
hsed /path/to/file replace 11#XJ 13#QR << 'EOF'
EOF
# Insert after a line
hsed /path/to/file append 13#QR << 'EOF'
inserted content
EOF
# Insert before a line
hsed /path/to/file prepend 11#XJ << 'EOF'
inserted content
EOF
# Preview (dry-run, no write)
hsed -p /path/to/file replace 11#XJ << 'EOF'
new content
EOF
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.
- 4d ago First seen · 123 lines · 40 tokens per session scan A b5abc8b8e721
hline-usage is a skill published in the GitHub repository chennest/hline (2 stars, last pushed 2mo ago), licensed MIT. It adds 40 tokens to every session and 1,085 once invoked, about $0.0002 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
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.