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/serac-labs/serac/discovery-patternsnpx skills add serac-labs/serac --skill discovery-patternsgit clone --depth 1 https://github.com/serac-labs/seracWrote 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/serac-labs/serac/discovery-patterns)<a href="https://agentmods.dev/skills/serac-labs/serac/discovery-patterns"><img src="https://agentmods.dev/badge/skills/serac-labs/serac/discovery-patterns.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 | $0.00040 | $0.02651 |
| Opus 5 | $0.00020 | $0.01326 |
| Sonnet 5 | $0.00008 | $0.00530 |
| Haiku 4.5 | $0.00004 | $0.00265 |
Grade A, and why
discovery-patterns 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 4d 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 — 392 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Discovery Patterns for ServiceNow
Discovery automatically populates the CMDB by scanning networks and systems.
Discovery Architecture
Discovery Schedule
↓
MID Server
↓
Probes (collect data)
↓
Sensors (process data)
↓
Identification Rules (match/create CIs)
↓
CMDB Population
Key Tables
| Table | Purpose |
|---|---|
discovery_schedule |
Discovery schedules |
discovery_credentials |
Discovery credentials |
discovery_range |
IP ranges to scan |
cmdb_identification_rule |
CI identification |
ecc_agent |
MID Server records |
discovery_status |
Discovery run status |
Discovery Schedules (ES5)
Create Discovery Schedule
// Create discovery schedule (ES5 ONLY!)
var schedule = new GlideRecord("discovery_schedule")
schedule.initialize()
// Basic info
schedule.setValue("name", "Data Center Discovery")
schedule.setValue("description", "Weekly discovery of data center infrastructure")
// Type
schedule.setValue("discover", "IP") // IP, CI, Cloud Resources
// Schedule
schedule.setValue("run_type", "weekly")
schedule.setValue("run_dayofweek", "sunday")
schedule.setValue("run_time", "02:00:00")
// MID Server
schedule.setValue("mid_server", getMIDServerSysId("DataCenterMID"))
// Enable
schedule.setValue("active", true)
var scheduleSysId = schedule.insert()
// Add IP range
addDiscoveryRange(scheduleSysId, "10.0.0.0", "10.0.255.255", "Data Center Network")
Add Discovery Range
// Add IP range to discovery schedule (ES5 ONLY!)
function addDiscoveryRange(scheduleSysId, startIP, endIP, name) {
var range = new GlideRecord("discovery_range")
range.initialize()
range.setValue("schedule", scheduleSysId)
range.setValue("name", name)
range.setValue("type", "range")
range.setValue("range_start", startIP)
range.setValue("range_end", endIP)
range.setValue("active", true)
return range.insert()
}
// Add CIDR range
function addDiscoveryCIDR(scheduleSysId, cidr, name) {
var range = new GlideRecord("discovery_range")
range.initialize()
range.setValue("schedule", scheduleSysId)
range.setValue("name", name)
range.setValue("type", "cidr")
range.setValue("range", cidr) // e.g., '10.0.0.0/24'
range.setValue("active", true)
return range.insert()
}
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.
- 4d ago First seen · 392 lines · 40 tokens per session scan A 9bbd504f2eb8
discovery-patterns is a skill published in the GitHub repository serac-labs/serac (78 stars, last pushed 9d ago), licensed Apache-2.0. It adds 40 tokens to every session and 2,651 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-08-30.
Other skills, from other repositories
hostinger-deploy
Hostinger-specific deployment protocol handling OPcache, CDN caching, and hPanel Git mechanism. Activates for "deploy to hostinger", "hostinger", "redeploy", "publish website", "push to production" when target is Hostinger.
infra-deploy
Infrastructure deployment for VPS, Docker, and cloud platforms. Activates for "deploy", "setup server", "docker", "coolify", "VPS", "SSH", "nginx", "production", "hosting" requests.
deploy-windows
Use this skill when installing, deploying, launching, serving, or troubleshooting mesh-llm on a Windows machine — PowerShell install via install.ps1, flavor selection (CUDA/ROCm/Vulkan/CPU), source builds, the contrib helper scripts, and verifying it serves.
quota-debug
Diagnose Kubernetes native ResourceQuota and LimitRange admission rejections (exceeded quota, forbidden by LimitRange, FailedCreate). Checks namespace quotas, current usage, LimitRange constraints, and ReplicaSet events to identify why pods cannot be created. Not applicable to Volcano Queue — use…
hpa-debug
Diagnose HorizontalPodAutoscaler failures (not scaling, metrics unavailable, target mismatch). Checks HPA status, metrics-server health, and scaling events to identify why autoscaling is not working.
scan-gke-clusters
Refresh the GKE TPU cluster inventory for one or more GCP projects. Runs .claude/scripts/scan-gke-clusters.sh to enumerate clusters with TPUs in each project (status, XPK presence, ready-node count, XPK type, topology, machine type), writes a per-project Markdown summary at .env/ -gke-tpu-cluster-scan.md, and merges…