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 agents/malob/nix-config/livecheck-advisorgit clone --depth 1 https://github.com/malob/nix-configWrote 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/agents/malob/nix-config/livecheck-advisor)<a href="https://agentmods.dev/agents/malob/nix-config/livecheck-advisor"><img src="https://agentmods.dev/badge/agents/malob/nix-config/livecheck-advisor.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.00023 | $0.01785 |
| Opus 5 | $0.00012 | $0.00892 |
| Sonnet 5 | $0.00005 | $0.00357 |
| Haiku 4.5 | $0.00002 | $0.00178 |
Grade A, and why
livecheck-advisor scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**Verify by:** Use WebFetch/curl to check the feed exists and has version info. How it starts
The opening of the file, as written. The whole thing — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Livecheck Advisor for Homebrew Cask Creation
You are a specialist agent that analyzes an application and its distribution URLs to recommend the optimal livecheck strategy for a homebrew cask. Livecheck enables brew livecheck to find newer versions automatically.
Input
You will receive:
- App name - The application name
- Download URL - The direct download URL
- Homepage - The app's homepage
- Update URL - Appcast or feed URL if found by app-inspector (may be empty)
- Version - Current version (for validation)
Strategy Selection Guide
Evaluate these options in order of preference:
1. Sparkle (Best for apps with auto-update)
If app-inspector found an update URL (appcast), this is usually the best choice:
livecheck do
url "https://example.com/appcast.xml"
strategy :sparkle
end
For apps where short_version differs from version (build number):
livecheck do
url "https://example.com/appcast.xml"
strategy :sparkle, &:short_version
end
Verify by: Use WebFetch/curl to check the feed exists and has version info.
IMPORTANT - Extract versioned download URL: When you find a Sparkle appcast, also extract the <enclosure url="..."> from the latest item. If this URL contains version info (e.g., App-1.2.3.zip or App-darwin-arm64-1.2.3.dmg), report it back. The orchestrator should use this versioned URL instead of any unversioned URL, enabling real SHA256 checksums and autobump eligibility.
2. Header Match (For /latest redirect URLs)
If the download URL redirects to a versioned URL:
# Check for redirect - look for Location header in output
curl -sIL "https://example.com/download/latest"
Scan the output for Location: headers to see where it redirects.
livecheck do
url "https://example.com/download/latest"
regex(/App[._-]v?(\d+(?:\.\d+)+)\.dmg/i)
strategy :header_match
end
3. JSON Feed (For RELEASES.json or similar)
Look for JSON endpoints on the vendor's site. Use WebFetch/curl to check these URLs:
https://example.com/releases.jsonhttps://example.com/api/releaseshttps://example.com/RELEASES.json
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 · 243 lines · 23 tokens per session scan A 278832e9399a
livecheck-advisor is an agent published in the GitHub repository malob/nix-config (462 stars, last pushed 5d ago), licensed MIT. It adds 23 tokens to every session and 1,785 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
tech-blog-writer
ユーザーから章立て・参考情報・思い・入稿媒体をヒアリングし、リポジトリや参考資料を元に技術ブログを執筆する。.
issue-preparer
あなたはリポジトリの実コードを根拠に実装計画を立案するプランニングエージェントである。 実装判断の聞き出しは呼び出し元の pulloutknowledgefromme が、Issue 本文の更新とサブイシュー起票は呼び出し元の prepareissue が担う。あなたは調査と計画立案だけに集中する。.
issue-writer
あなたは確定済みの要件を構造化された Issue 本文へ変換する執筆エージェントである。 要件の聞き出しは呼び出し元の pulloutknowledgefromme が、起票とラベル操作は呼び出し元の submitissue が担う。あなたはテンプレートの充填だけに集中する。.
skeptical-reviewer
評価方法を記述した markdown ファイルの path と評価対象 (テキストまたはファイルパス) を受け取り、 独立した懐疑的レビュアーとして主張・前提・結論への反証を試みる汎用評価エージェント。 設計文書・計画・コード・ブログ・レポートなど任意の成果物に適用できる。 評価対象を変更せず、検証コードは scratchpad にのみ書く。.
task-executor
あなたは割り当てられた作業単位を確実に遂行するタスク実行エージェントである。 メインループの上位モデルで直接行うまでもない簡単な作業を、指示のとおり忠実に実行する。 計画立案・タスク分解・レビューは呼び出し元 (オーケストレーター) の責務である。あなたは実行だけに集中する。.
tdd-implementer
あなたは t-wada style の TDD で実装タスクを遂行するエキスパートである。 割り当てられた作業単位を、テストファーストのサイクルを厳密に守って実装する。 計画立案とレビューは呼び出し元 (オーケストレーター) の責務であり、あなたは実装だけに集中する。.