hn-summarize — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited hn-summarize (Agent Skill) and scored it 96/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 1 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 1 flagged
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
hckrnews.com is a JavaScript-rendered front end - curling it returns an empty shell, so do not scrape it. Instead use the official Hacker News APIs (Firebase + Algolia), which give the same stories with points, comment counts, and full comment trees. These APIs return plain JSON, so plain curl works fine.
topstories.json returns 500 story IDs in front-page rank order. Take the first N and look up each item.
curl -sL 'https://hacker-news.firebaseio.com/v0/topstories.json' -o /tmp/top.json
python3 -c "
import json,urllib.request
ids=json.load(open('/tmp/top.json'))[:10]
for i,sid in enumerate(ids,1):
d=json.load(urllib.request.urlopen(f'https://hacker-news.firebaseio.com/v0/item/{sid}.json'))
print(f\"{i}. {d.get('title')} | {d.get('score')} pts | {d.get('descendants',0)} comments | id {sid}\")
print(f\" {d.get('url','(text post)')}\")
"curl -sL 'https://hn.algolia.com/api/v1/search?query=YOUR+QUERY&tags=story' -o /tmp/s.json
python3 -c "
import json
for h in json.load(open('/tmp/s.json'))['hits'][:8]:
print(h['objectID'], '|', h.get('points'), 'pts |', h.get('num_comments'), 'comments |', h['title'])
print(' ', h.get('url'))
"&numericFilters=created_at_i>UNIXTS to restrict to recent stories (avoids matching an old duplicate of the same headline).search ranks by relevance; search_by_date ranks by recency.objectID with the highest points/comments - that's the live front-page discussion.curl -sL 'https://hn.algolia.com/api/v1/items/OBJECT_ID' -o /tmp/hn.jsonThe response is a nested tree: top-level children are root comments, each with their own children. Flatten and print root comments in thread order (HN's default ranking ≈ this order):
python3 -c "
import json,re
d=json.load(open('/tmp/hn.json'))
def clean(t):
t=re.sub('<[^>]+>',' ',t)
for a,b in [(''',chr(39)),('>','>'),('<','<'),('&','&'),('"','\"')]:
t=t.replace(a,b)
return re.sub(' +',' ',t).strip()
for c in d.get('children',[])[:15]:
if c.get('text'):
print(f\"{c.get('author')}: {clean(c['text'])[:550]}\")
print('---')
"Note: Algolia's per-comment points field is now always null, so sort by thread order (already roughly HN's ranking) rather than by points. For deeper threads, recurse into children and track depth.
Fetch the story's article with curl -sL <url>, then strip tags with sed 's/<[^>]*>//g' to extract readable text, or grep for the key sentences. If the page is JS-heavy or paywalled, try a Wayback Machine snapshot:
curl -sL 'http://archive.org/wayback/available?url=ARTICLE_URL' -o /tmp/wb.json
python3 -c "import json;print(json.load(open('/tmp/wb.json'))['archived_snapshots'].get('closest',{}).get('url'))"Then fetch the snapshot URL the same way. If the host blocks outbound curl requests, fetch through a container or proxy you have available.
For each story give: title, points, comment count, source, a few sentences on what the article says, then comment themes - group the discussion into 3-6 recurring threads (agreement, rebuttals, tangents) rather than listing comments one by one. Note when the top thread is a critical/contrarian take, since that's common on HN.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.