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 ArabelaTso/Skills-4-SE --skill code-instrumentation-generatorgit clone --depth 1 https://github.com/ArabelaTso/Skills-4-SEWrote 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/arabelatso/skills-4-se/code-instrumentation-generator)<a href="https://agentmods.dev/skills/arabelatso/skills-4-se/code-instrumentation-generator"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/code-instrumentation-generator/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/arabelatso/skills-4-se/code-instrumentation-generator"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/code-instrumentation-generator.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.00109 | $0.02066 |
| Opus 5 | $0.00055 | $0.01033 |
| Sonnet 5 | $0.00022 | $0.00413 |
| Haiku 4.5 | $0.00011 | $0.00207 |
Grade A, and why
code-instrumentation-generator 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 9d 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 — 350 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Instrumentation Generator
Automatically instrument source code to collect runtime information while preserving program semantics.
Workflow
Follow these steps to instrument code:
1. Analyze the Source Code
Understand the code structure and identify instrumentation points:
- Language detection: Identify the programming language
- Code structure: Parse functions, classes, branches, loops
- Entry/exit points: Locate function boundaries
- Control flow: Identify branches (if/else, switch, loops)
- Variable scope: Understand variable declarations and usage
2. Determine Instrumentation Strategy
Choose appropriate instrumentation based on requirements:
Instrumentation levels:
- Function-level: Entry/exit of functions with parameters and return values
- Branch-level: Execution of conditional branches (if/else, switch cases)
- Statement-level: Individual statement execution
- Variable-level: Variable assignments and value changes
Configuration options:
- Enable/disable specific instrumentation types
- Filter by function names or file patterns
- Set verbosity level
- Choose output format (logs, JSON, CSV)
3. Insert Instrumentation Code
Add instrumentation hooks at identified points:
Function instrumentation:
- Insert entry hook at function start
- Capture function name, parameters, timestamp
- Insert exit hook before returns
- Capture return value, execution time
Branch instrumentation:
- Insert hooks at branch conditions
- Record which branch was taken
- Track branch coverage
Variable instrumentation:
- Insert hooks after variable assignments
- Capture variable name and value
- Track value changes over time
4. Ensure Semantic Preservation
Verify that instrumentation doesn't change program behavior:
- No side effects: Instrumentation code doesn't modify program state
- Exception safety: Instrumentation handles exceptions properly
- Performance: Minimal overhead added
- Thread safety: Instrumentation is safe in concurrent code
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.
- 9d ago First seen · 350 lines · 109 tokens per session scan A 88a0050c72fe
code-instrumentation-generator is a skill published in the GitHub repository ArabelaTso/Skills-4-SE (251 stars, last pushed 19d ago), licensed Apache-2.0. It adds 109 tokens to every session and 2,066 once invoked, about $0.0005 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
perf-profiler
A performance investigation guide that uses repeatable measurements and profiling evidence to find where software spends time or resources. Profiling records runtime activity such as CPU use, memory use, database work, or network delays.
log-analyzer
A log-analysis helper that reads application and system logs to find unusual patterns and likely causes. Logs are records of events such as errors, requests, warnings, and service activity.
trace
Trace Elixir call trees from entry points via mix xref. Use when debugging data flow, planning signature changes, or understanding how a bug reaches code.
code-review-web
Review web application code for bugs, security issues, performance problems, and stack-specific anti-patterns. Use this skill whenever the user wants to review code, debug a production issue, investigate a build failure, audit security, or check a PR before merging. Triggers on code review, review my code, debug…
bim-consistency-checker
Check BIM model consistency: naming conventions, parameter completeness, spatial relationships, and data integrity across model elements.
check-tools
Validates development tool installations across Python, Node.js, Java, Go, Rust, C/C++, Git, and system utilities. Use when verifying environments or troubleshooting dependencies.