Borrowing it
Nothing to install: this file belongs to jtmoon79/super-speedy-syslog-searcher. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jtmoon79/super-speedy-syslog-searcher/main/.claude/skills/ere-regex-increment/SKILL.mdgit clone --depth 1 https://github.com/jtmoon79/super-speedy-syslog-searcherWrote 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/jtmoon79/super-speedy-syslog-searcher/ere-regex-increment)<a href="https://agentmods.dev/skills/jtmoon79/super-speedy-syslog-searcher/ere-regex-increment"><img src="https://agentmods.dev/badge/skills/jtmoon79/super-speedy-syslog-searcher/ere-regex-increment/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/jtmoon79/super-speedy-syslog-searcher/ere-regex-increment"><img src="https://agentmods.dev/badge/skills/jtmoon79/super-speedy-syslog-searcher/ere-regex-increment.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00058 | $0.00734 |
| Opus 5 | $0.00029 | $0.00367 |
| Sonnet 5 | $0.00012 | $0.00147 |
| Haiku 4.5 | $0.00006 | $0.00073 |
Grade A, and why
ere-regex-increment 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 11d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ERE Regex Increment
Use this skill to renumber ERE_REGEX_DATETIME! declarations in subprojects/ere/ere_datetimes_impl/src/ere_datetimes_impl.rs when a new datetime regex is inserted or an existing run needs to shift.
The workflow updates the declaration identifier, not datetime test expectations or match offsets.
Target Pattern
Each declaration has two paired identifiers that must stay equal:
#[cfg(any(regex = "N", regex = "ALL"))]
ERE_REGEX_DATETIME!(
N,
counter!(DP_KEY),
// ...
)
Some declarations include extra cfg selectors, such as regex = "TEST". Preserve all non-numeric selectors and only change the numeric regex id for the declaration being renumbered.
Preflight
- Read the target area in
subprojects/ere/ere_datetimes_impl/src/ere_datetimes_impl.rs. - Identify the exact starting declaration from the user's line number, regex id, nearby comment, or example text.
- If the same numeric id appears more than once near the start point, use the line number or surrounding comment to choose the intended declaration. Ask a short clarification only if the start declaration is genuinely ambiguous.
- Determine the increment amount. Default to
+1when the user says increment, shift, bump, or make room. - Find the last declaration in the affected run and the current value of
DATETIME_PARSE_DATAS_LEN_MAX.
Edit Rules
For each affected ERE_REGEX_DATETIME! declaration, update exactly these values in lockstep:
- The numeric
regex = "N"selector inside the immediately preceding#[cfg(any(...))]attribute. - The first numeric argument inside the immediately following
ERE_REGEX_DATETIME!invocation.
Do not change:
- Test-vector tuple values inside the
&[...]examples. - Date, time, offset, or expected parse tuple values.
- Comments, examples, declaration order, or regex pattern text.
- Other cfg selectors such as
regex = "ALL"orregex = "TEST". - Unrelated numeric literals in the macro body.
If the final declaration id changes, update DATETIME_PARSE_DATAS_LEN_MAX to the new highest declaration id.
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.
- 11d ago First seen · 76 lines · 58 tokens per session scan A 44b23970a791
ere-regex-increment is a skill published in the GitHub repository jtmoon79/super-speedy-syslog-searcher (59 stars, last pushed 3d ago), licensed MIT. It adds 58 tokens to every session and 734 once invoked, about $0.0003 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
rust-patterns
Idiomatic Rust patterns, ownership, error handling, traits, concurrency, and best practices for building safe, performant applications.
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.
omh-rust
This is a Hermes-native rust workflow skill.
opentelemetry-net-instrumentation
Provides guidance for implementing OpenTelemetry instrumentation in .NET codebases, covering tracing (Activities/Spans), metrics, logs, naming conventions, error handling, performance, SDK setup, resources, context propagation, and API design best practices.
bevy-ecs
Structure a Bevy app around its Entity Component System: build the App with plugins, define Component/Resource types, write systems with Query/Res/Commands, filter and order systems, and use the Time resource for frame-rate-independent motion. Use when building or debugging a Bevy game in Rust — when the user mentions…
rust-project
Modern Rust project architecture guide for 2025. Use when creating Rust projects (CLI, web services, libraries). Covers workspace structure, error handling, async patterns, and idiomatic Rust best practices.