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 wangke19/gemini-ai-helpers --skill system-config-analysisgit clone --depth 1 https://github.com/wangke19/gemini-ai-helpersWrote 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/wangke19/gemini-ai-helpers/system-config-analysis)<a href="https://agentmods.dev/skills/wangke19/gemini-ai-helpers/system-config-analysis"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/system-config-analysis/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/wangke19/gemini-ai-helpers/system-config-analysis"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/system-config-analysis.svg" alt="Reviewed on agentmods" width="80" 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.00046 | $0.04248 |
| Opus 5 | $0.00023 | $0.02124 |
| Sonnet 5 | $0.00009 | $0.00850 |
| Haiku 4.5 | $0.00005 | $0.00425 |
Grade A, and why
System Configuration Analysis 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 8d 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 — 547 lines — stays where its author put it; the contents beside it link to each section on GitHub.
System Configuration Analysis Skill
This skill provides detailed guidance for analyzing system configuration from sosreport archives, including OS information, installed packages, systemd services, and SELinux/AppArmor settings.
When to Use This Skill
Use this skill when:
- Analyzing the
/sosreport:analyzecommand's system configuration phase - Investigating service failures or misconfigurations
- Verifying package versions and updates
- Checking security policy settings (SELinux/AppArmor)
- Understanding system state and configuration
Prerequisites
- Sosreport archive must be extracted to a working directory
- Path to the sosreport root directory must be known
- Understanding of Linux system administration
Key Configuration Data Locations in Sosreport
-
System Information:
uname- Kernel versionetc/os-release- OS distribution and versionuptime- System uptimeproc/uptime- Uptime in secondssos_commands/release/- Release information
-
Package Information:
installed-rpms- RPM packages (RHEL/Fedora/CentOS)installed-debs- DEB packages (Debian/Ubuntu)sos_commands/yum/- Yum/DNF informationsos_commands/rpm/- RPM database queries
-
Service Status:
sos_commands/systemd/systemctl_list-units- All unitssos_commands/systemd/systemctl_list-units_--failed- Failed unitssos_commands/systemd/systemctl_status_--all- Detailed service statussos_commands/systemd/systemctl_list-unit-files- Unit files
-
SELinux:
sos_commands/selinux/sestatus- SELinux statussos_commands/selinux/getenforce- Current enforcement modesos_commands/selinux/selinux-policy- Policy informationvar/log/audit/audit.log- SELinux denials
-
AppArmor (if applicable):
sos_commands/apparmor/- AppArmor configurationetc/apparmor.d/- AppArmor profiles
-
System Configuration Files:
etc/- System-wide configurationetc/sysctl.conforetc/sysctl.d/- Kernel parametersetc/security/limits.conf- Resource limits
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.
- 8d ago First seen · 547 lines · 46 tokens per session scan A 3b5083ced094
System Configuration Analysis is a skill published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 46 tokens to every session and 4,248 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-09-03.
Other skills, from other repositories
gcloud-usage
This skill should be used when user asks about "GCloud logs", "Cloud Logging queries", "Google Cloud metrics", "GCP observability", "trace analysis", or "debugging production issues on GCP".
lov-obsidian-ensure-dev-sync
A troubleshooting workflow for an Obsidian plugin development chain: building the plugin, copying its files into an Obsidian Vault, and checking hot reload. An Obsidian Vault is the folder where Obsidian stores notes and plugin files.
lov-fix-by-add-log
A debugging assistant that adds a small amount of targeted diagnostic logging and uses the resulting output to investigate a hard-to-reproduce problem.
lov-fix-general
A software troubleshooting workflow for finding the cause of an error, applying a focused fix, and checking the original failing path again.
lov-fix-until-no-error
A verification-focused debugging workflow that repeatedly runs specified checks, fixes the highest-priority failure, and stops when the checks pass or a genuine external blockage remains.
vault-lint
Use when the user wants a health audit of the vault — stale content, provenance drift, frontmatter compliance, or MOC coverage gaps. Triggers on "lint vault", "vault health", "check vault", "stale notes", "vault audit", "vault quality", or "check conventions".