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 scitix/siclaw --skill node-logsgit clone --depth 1 https://github.com/scitix/siclawWrote 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/scitix/siclaw/node-logs)<a href="https://agentmods.dev/skills/scitix/siclaw/node-logs"><img src="https://agentmods.dev/badge/skills/scitix/siclaw/node-logs/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/scitix/siclaw/node-logs"><img src="https://agentmods.dev/badge/skills/scitix/siclaw/node-logs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, 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 Privilege Escalation · line 81 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 82 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 81 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00084 | $0.03220 |
| Opus 5.5 | $0.00034 | $0.01288 |
| Sonnet 5.5 | $0.00017 | $0.00644 |
| Haiku 4.5 | $0.00008 | $0.00322 |
Grade A, and why
node-logs 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 1mo 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 — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Node Logs
Read this first: what an empty result means
Every command here can come back with nothing, and the reason matters more than
the emptiness. So both scripts print exactly one status: line and it is always
the last line of the output, with any explanation above it — one rule, every
outcome. (A bad argument is rejected on stderr with exit 2 before any report, so
there is no status line to read in that case.)
status: |
Meaning | What you may conclude |
|---|---|---|
ok |
Source read, lines matched | Read the lines |
no_match |
Source read fine, filter matched nothing | Nothing about the node. Bounded non-evidence for that one query |
source_error |
The log source itself failed (see stderr) | Nothing — the output above it is partial |
filter_error |
Your pattern was rejected; nothing was searched | Nothing — fix the pattern and rerun |
not_found / not_a_log_file / empty_source |
The path is wrong, is a directory, or the handler is off | Nothing about the node's health |
query_unsupported |
This kubelet cannot serve journald over the API | Nothing — use a file, or tier 1/2 |
forbidden |
The agent lacks nodes/proxy |
Nothing — an access fact, not a node fact |
no_match is the one that gets misread. "No PLEG messages in the last hour" is
not "PLEG is healthy": journald retention, a --since that misses the event, a
unit that never logged to this source, and a pattern that does not match this
component's wording all produce it. Report what you queried, not just that it
was empty. The header's scanned: count is what tells you whether anything was
actually read.
Pick an access path
Try them in this order and say which one produced the evidence.
Tier 1 — host_script (preferred)
The node is a bound SSH host: check host_list by node name or IP. No debug pod,
lowest latency.
One caveat that produces empty results: journalctl only shows the system
journal to root and to members of adm / systemd-journal. An ordinary SSH
account gets its own messages and exit 0 — so a system unit looks like it
logged nothing. The script detects that account state, says so in a note:, and
repeats it in the no_match explanation. When you see it, the answer is not
"the unit was quiet": rerun via node_script, which enters the host namespaces
as root.
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.
- 1mo ago First seen · 252 lines · 84 tokens per session scan A 7485f54284d5
node-logs is a skill published in the GitHub repository scitix/siclaw (238 stars, last pushed 6d ago), licensed Apache-2.0. It adds 84 tokens to every session and 3,220 once invoked, about $0.0003 per session on Opus 5.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-30.
Other skills, from other repositories
k8s-deployment-rollout
A troubleshooting workflow for failed Kubernetes Deployment releases and rolling updates that become stuck. Kubernetes is a system for running and managing containers.
k8s-pod-crashloop
A troubleshooting guide for Kubernetes pods that repeatedly restart or run out of memory. Kubernetes is a system for running and managing containers, and a pod is its basic unit for running an application.
k8s-incident-triage
Read-only Kubernetes incident triage using kubectl. Accepts natural language or structured input. Produces root-cause hypotheses, evidence, and next-step commands.
kubernetes-expert
Expert-level Kubernetes cluster management, deployment strategies, networking, and production operations. Use when the user mentions containers, orchestration, devops, or cloud native, or when the task involves Kubernetes Architecture, Pods, Deployments, or Services.
lucas-runbook
Lucas runbook-driven troubleshooting for Kubernetes issues. Use when investigating pod errors, crashes, restarts, or any Kubernetes problem. Automatically search runbooks before taking action.
ariadne-kubernetes-graph
Use for Ariadne MCP-backed Kubernetes state questions: translate operational questions into Cypher, repair graphquery failures, and decide when graphschema or graphhealth is needed. Best for live or snapshot-backed graph data about resource relationships; do not use for codebase-only tasks or generic Kubernetes…