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 divinevideo/divine-mobile --skill gorse-05-config-migrationgit clone --depth 1 https://github.com/divinevideo/divine-mobileWrote 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/divinevideo/divine-mobile/gorse-05-config-migration)<a href="https://agentmods.dev/skills/divinevideo/divine-mobile/gorse-05-config-migration"><img src="https://agentmods.dev/badge/skills/divinevideo/divine-mobile/gorse-05-config-migration/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/divinevideo/divine-mobile/gorse-05-config-migration"><img src="https://agentmods.dev/badge/skills/divinevideo/divine-mobile/gorse-05-config-migration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Anti-Refusal · line 20 Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.Fix: Remove instructions that suppress warnings, disclaimers, or ethical commentary. Let the agent surface safety-relevant caveats to the user.
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.00160 | $0.01608 |
| Opus 5 | $0.00080 | $0.00804 |
| Sonnet 5 | $0.00032 | $0.00322 |
| Haiku 4.5 | $0.00016 | $0.00161 |
Grade A, and why
gorse-05-config-migration 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 6d 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gorse 0.5.x Config Migration from 0.4
Problem
Gorse 0.5 introduced breaking config changes from 0.4. Old config sections are silently ignored (no error, no warning), making it appear that features like collaborative filtering, trending, and item neighbors are configured when they're actually disabled.
The most critical issue: [recommend.collaborative] defaults to type = "none" in 0.5, meaning
collaborative filtering is silently disabled unless you explicitly set type = "mf".
Context / Trigger Conditions
- Gorse 0.5.x is deployed but recommendations seem random or low quality
- Collaborative filtering doesn't seem to work despite config having
[recommend.collaborative] - Config has old 0.4 sections:
[recommend.popular],[recommend.neighbors],[recommend.online],[recommend.offline] - Upgrading from Gorse 0.4 to 0.5
- Gorse master starts successfully but old config features don't take effect
Solution
Removed 0.4 Sections (silently ignored in 0.5)
| 0.4 Section | 0.5 Replacement |
|---|---|
[recommend.popular] |
[[recommend.non-personalized]] (TOML array of tables) |
[recommend.neighbors] |
[[recommend.item-to-item]] + [[recommend.user-to-user]] |
[recommend.online] (explore/exploit) |
[recommend.ranker] (FM or LLM-based) |
[recommend.offline] |
[recommend.ranker] cache_expire + [recommend.fallback] |
Removed 0.4 Keys (do not exist in 0.5)
enable_item_neighbor_indexenable_user_neighbor_indexitem_neighbor_typeneighbor_typeexplore_recommendpopular_window
Critical Fix: Enable Collaborative Filtering
# 0.4 style (BROKEN in 0.5 — CF silently disabled):
[recommend.collaborative]
fit_period = "60m"
fit_epoch = 100
# 0.5 style (WORKING — must add type = "mf"):
[recommend.collaborative]
type = "mf"
fit_period = "60m"
fit_epoch = 100
Complete 0.5 Config Template
[recommend]
cache_size = 100
cache_expire = "72h"
context_size = 100
[recommend.data_source]
positive_feedback_types = ["reaction", "comment", "repost"]
read_feedback_types = ["view"]
positive_feedback_ttl = 0
item_ttl = 0
# Collaborative filtering — MUST set type = "mf" to enable
[recommend.collaborative]
type = "mf"
fit_period = "60m"
fit_epoch = 100
optimize_period = "360m"
optimize_trials = 10
[recommend.collaborative.early_stopping]
patience = 10
# Trending/popular — TOML array syntax [[...]] for multiple leaderboards
[[recommend.non-personalized]]
name = "trending_weekly"
score = "count(feedback, .FeedbackType == 'reaction') + count(feedback, .FeedbackType == 'comment') * 2"
filter = "(now() - item.Timestamp).Hours() < 168"
# Content-based item similarity (requires items to have Labels)
[[recommend.item-to-item]]
name = "similar_content"
type = "tags" # matches on item Labels
# Collaborative item similarity
[[recommend.item-to-item]]
name = "also_liked"
type = "users" # users who liked X also liked Y
# User similarity
[[recommend.user-to-user]]
name = "similar_users"
type = "items" # users who share liked items
# FM ranker blends all candidate sources
[recommend.ranker]
type = "fm" # or "llm" for LLM-based reranking
recommenders = ["latest", "collaborative", "non-personalized/trending_weekly", "item-to-item/similar_content", "item-to-item/also_liked", "user-to-user/similar_users"]
fit_period = "60m"
fit_epoch = 100
[recommend.ranker.early_stopping]
patience = 10
[recommend.fallback]
recommenders = ["latest"]
[recommend.replacement]
enable_replacement = true
positive_replacement_decay = 0.8
read_replacement_decay = 0.6
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.
- 6d ago First seen · 169 lines · 160 tokens per session scan A 65e6299b38a2
gorse-05-config-migration is a skill published in the GitHub repository divinevideo/divine-mobile (265 stars, last pushed today), licensed MPL-2.0. It adds 160 tokens to every session and 1,608 once invoked, about $0.0008 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-09-03.
Other skills, from other repositories
printing-press-amend
Amend a published CLI from one of two input sources: (1) dogfood mode mines the active Claude Code session transcript for friction (missing flags, hand- rolled API payloads, silent-null returns); (2) direct-input mode accepts user-supplied asks (rename a command, add commands or feeds, fix a named bug, optionally…
convex-performance-audit
Audits Convex performance for reads, subscriptions, write contention, and function limits. Use for slow features, insights findings, OCC conflicts, or read amplification.
convex-insights
Query a running Convex app's logs + health in natural language (official MCP): failures, slow/expensive functions, deploy causality — scoped, evidence-backed, with a dashboard deep link.
ssl-proxy-troubleshoot
Systematic workflow for troubleshooting SSL/proxy connectivity issues with government websites.
diagnose-backend-bug
Diagnose a bounded backend or multi-service failure from GitHub Issues, Jira, Aone, user-provided exports, logs, traces, responses, stack traces, or job records. Use when a service, API, RPC, worker, queue, CLI, or scheduled job bug needs correlation through the project's existing observability route before repair; do…
axiom-networking
Use when implementing or debugging ANY network connection, API call, or socket. Covers URLSession, Network.framework, NetworkConnection, connection diagnostics.