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/rhtevan/agentfs/fedora-dns-cachenpx skills add rhtevan/agentfs --skill fedora-dns-cachegit clone --depth 1 https://github.com/rhtevan/agentfsWrote 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/rhtevan/agentfs/fedora-dns-cache)<a href="https://agentmods.dev/skills/rhtevan/agentfs/fedora-dns-cache"><img src="https://agentmods.dev/badge/skills/rhtevan/agentfs/fedora-dns-cache.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.1 | $0.00022 | $0.00890 |
| Opus 5 | $0.00011 | $0.00445 |
| Sonnet 5 | $0.00004 | $0.00178 |
| Haiku 4.5 | $0.00002 | $0.00089 |
Grade B, and why
fedora-dns-cache scanned grade B 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 5d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo mkdir -p /etc/systemd/resolved.conf.d 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.
Fedora DNS Cache for Offline Resilience
Configure systemd-resolved to serve stale (expired) DNS cache entries
when upstream DNS servers are unreachable, preventing 30+ second hangs
in terminals and shells caused by DNS resolution timeouts.
Problem
When an ISP connection drops or DNS servers become unreachable, every DNS lookup (hostname resolution, SSSD/IPA checks, etc.) blocks for 30+ seconds waiting for a timeout. This makes GNOME Terminal appear stuck — the window opens but no prompt appears until all pending DNS queries time out.
Solution
Enable StaleRetentionSec in systemd-resolved. When upstream DNS
is unreachable, previously cached answers are served immediately
(for up to 1 hour after expiry) instead of waiting for a timeout.
Prerequisites
- Fedora 40+ (or any systemd 250+ distro with
systemd-resolved) systemd-resolvedactive as the system DNS resolversudoaccess to write to/etc/systemd/resolved.conf.d/
Steps
-
Diagnose DNS timeout history
Check if DNS timeouts have been occurring:
resolvectl statistics | grep -A1 TimeoutAny non-zero "Total Timeouts" confirms the problem.
-
Check current configuration
Verify no existing stale cache config:
systemd-analyze cat-config systemd/resolved.conf | grep -i staleDefault is
#StaleRetentionSec=0(disabled). -
Apply the drop-in configuration
Run the setup script (requires
sudo):bash ~/.agents/skills/fedora-dns-cache/scripts/setup.shOr apply manually:
sudo mkdir -p /etc/systemd/resolved.conf.d sudo tee /etc/systemd/resolved.conf.d/fast-timeout.conf <<'EOF' # Reduce DNS pain when ISP connection drops [Resolve] # Serve stale (expired) cached records when upstream DNS is unreachable # rather than waiting for a timeout. Stale records served for up to 1 hour. StaleRetentionSec=3600 EOF -
Restart systemd-resolved
sudo systemctl restart systemd-resolved
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 123 lines · 22 tokens per session scan B a0c4dee1c2d3
fedora-dns-cache is a skill published in the GitHub repository rhtevan/agentfs (2 stars, last pushed today), licensed Apache-2.0. It adds 22 tokens to every session and 890 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…