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 agrc/agent-skills --skill ugrc-lsof-warning-filtergit clone --depth 1 https://github.com/agrc/agent-skillsWrote 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/agrc/agent-skills/ugrc-lsof-warning-filter)<a href="https://agentmods.dev/skills/agrc/agent-skills/ugrc-lsof-warning-filter"><img src="https://agentmods.dev/badge/skills/agrc/agent-skills/ugrc-lsof-warning-filter/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/agrc/agent-skills/ugrc-lsof-warning-filter"><img src="https://agentmods.dev/badge/skills/agrc/agent-skills/ugrc-lsof-warning-filter.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.00023 | $0.00350 |
| Opus 5 | $0.00012 | $0.00175 |
| Sonnet 5 | $0.00005 | $0.00070 |
| Haiku 4.5 | $0.00002 | $0.00035 |
Grade A, and why
ugrc-lsof-warning-filter 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.
What it actually says
I’m seeing lots of lsof warnings in my terminal when I start the Firebase emulators in this project. Please:
- Inspect the project to find every existing
firebase emulators:startinvocation, especially inpackage.jsonscripts. - Create a bash script wrapper that starts the emulators but filters out only the noisy
lsof-related warnings from stderr, similar to this pattern:
#!/bin/bash
# Keep Firebase emulator output intact while filtering noisy macOS lsof warnings.
args=()
for arg in "$@"; do
if [[ "$arg" != "--" ]]; then
args+=("$arg")
fi
done
firebase emulators:start "${args[@]}" 2> >(grep -Ev 'lsof|Output information may be incomplete|assuming "dev=.*" from mount table' >&2)
- Preserve the exact Firebase CLI arguments already used by this project so no existing functionality is lost.
- Replace the direct Firebase emulator CLI calls in
package.jsonwith calls to the new script. - Make the smallest change possible and keep the project’s existing style and structure.
- Validate the result with a focused check, preferably by verifying the script syntax and confirming the updated package scripts still invoke Firebase correctly without changing their behavior.
- Tell me exactly what changed and note any caveats.
If the project uses multiple emulator commands with different flags, the script should support forwarding those arguments correctly.
If needed, place the script in a sensible repo location like scripts/firebase-emulators.sh.
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 · 34 lines · 23 tokens per session scan A 5fe06d5b4615
ugrc-lsof-warning-filter is a skill published in the GitHub repository agrc/agent-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 350 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
performance-optimization
Optimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.
gke-ai-troubleshooting-jobset-interruption
Diagnoses GKE JobSet interruptions, restarts, and preemptions for AI/ML training workloads autonomously. Use when troubleshooting JobSet restart loops, spot VM preemptions, node readiness failures, host VM issues, or coordinator worker crashes. Don't use for general GKE cluster creation, basic workload deployment, or…
gke-node-notready
Diagnoses GKE nodes reporting NotReady or Unknown status by inspecting node conditions, events, kubelet/containerd logs, and node metrics, then proposing safe remediations. Use when nodes show NotReady, when the kubelet stops posting node status, or when workloads are evicted or stuck Pending due to node health. Don't…
gke-ai-troubleshooting-tpu-vbar-oom
Diagnoses and prevents vbarcontrolagent segfaults, out-of-memory (OOM) errors, and TPU device initialization failures on TPU v6e nodes in GKE caused by race conditions during TPU device resets or high-frequency metrics polling. Use when troubleshooting vbarcontrolagent crashes, memory cgroup OOMs in serial console…
systematic-debugging
A step-by-step method for finding the underlying cause of technical problems before changing code. It covers reading errors, reproducing failures, checking recent changes, and tracing data across system components.
fixing-motion-performance
Audit and fix animation performance issues including layout thrashing, compositor properties, scroll-linked motion, and blur effects. Use when animations stutter, transitions jank, or reviewing CSS/JS animation performance.