- Home
- Skills
- Code Quality & Review
- TelemetryShield – Static AST Instrumentation Integrity Guard
Works with the AI Agents you already use
TelemetryShield – Static AST Instrumentation Integrity Guard
Catches silently removed logs, metrics, and tracing spans during AI refactoring before your monitoring goes blind. Returns JSON.
$5
TelemetryShield – Static AST Instrumentation Integrity Guard
Example session with this skill installed
Run TelemetryShield on the live/ directory to verify our logging and tracing integrity before shipping the patch.
- Read your context and instructions
- Compiled the telemetryshield
🔍 ARCHITECTURAL COMPLIANCE SECURED. ENFORCING TELEMETRY INTEGRITY AUDIT BLUEPRINT ONLY.
--- INPUT — live/scan1.py ---
"""Live run 1: tracing span removed during refactor."""
from opentelemetry import trace
tracer = trace.get_tracer(name)
def process(records):
for record in records:
# process_record span removed during refactor
result = transform(record)
save(result)
--- INPUT — live/scan2.py ---
"""Live run 2: metric renamed and log call removed without authorization."""
import logging
logger = logging.getLogger(name)
def handle(request):
# logger.info("handling request %s", request.id) removed
counter.add(1, {"metric": "items_done"}) # was 'records_processed'
return build_response(request)
--- AUDIT OUTPUT ---
{
"audit_status": "CRITICAL",
"findings": [
{
"id": "f1",
"file": "live/scan1.py",
"line": 9,
"severity": "HIGH",
"signature": "OBSERVABILITY_REGRESSION",
"message": "tracing span 'process_record' was removed from the patched file",
"snippet": "# process_record span removed during refactor"
},
{
"id": "f2",
"file": "live/scan2.py",
"line": 10,
"severity": "MEDIUM",
"signature": "TELEMETRY_LAYOUT_MUTATION",
"message": "metric name changed from 'records_processed' to 'items_done' without authorization",
"snippet": "counter.add(1, {\"metric\": \"items_done\"})"
},
{
"id": "f3",
"file": "live/scan2.py",
"line": 9,
"severity": "HIGH",
"signature": "UNAUTHORIZED_INSTRUMENTATION_REMOVAL",
"message": "removal of logger.info call has no explicit user authorization",
"snippet": "# logger.info(\"handling request %s\", request.id) removed"
}
],
"metadata": {
"version": "1.2.0",
"timestamp": "2026-10-16T12:00:00Z",
"files_scanned": 2,
"calls_found": 3
}
}
--- VALIDATOR ---
PASS: live/live_run_report.json
Live run: PASS — 2 files evaluated, 3 structural instrumentation defects quarantined.
Connects securely to your tools. The creator never sees your data.
About this skill
Stop allowing autonomous coding models to silently blind your production monitoring stack during automated optimization tasks. TelemetryShield is a static AST-driven integrity guard built to lock, track, and verify observability infrastructure bindings before any refactored code block is finalized.
When AI agents clean up nested loops or rewrite complex routing modules, they repeatedly drop telemetry hooks to simplify logical execution paths. This results in severe production blindness without failing local compilation metrics. This engine isolates instrumentation regressions and outputs a strict, machine-readable JSON report.
Core Capabilities
- Observability Regression Isolation: Instantly catches silently deleted OpenTelemetry spans, structured logs, and metrics counters.
- Instrumentation Mutation Auditing: Flags unauthorized renaming of metric keys and context identifiers that break downstream dashboards.
- Automated Pipeline Verification: Emits a schema-validated, flat JSON payload optimized for Git pre-commit hooks and CI/CD pipelines.
- 100% Local & Air-Gapped Operations: Functions entirely offline with zero network traffic and zero risk of corporate repository exposure.
When to use
- Modifying high-throughput production microservices where OpenTelemetry specifications are strictly enforced.
- Reviewing automated refactoring tasks generated by coding frameworks like Claude Code or Cursor.
When NOT to use
- Local prototyping or ephemeral scratchpad code tracks lacking system logging hooks.
- Code blocks where application performance benchmarking explicitly requires completely clean, un-instrumented runtime configurations.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Code Quality & Review.
Static AST analysis constraints only. Inspects source syntax trees and context commentary paths without dynamic execution. Detects standardized signatures (OpenTelemetry, native loggers) and requires manual schema mapping for highly customized, proprietary framework wrappers.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 22 days ago
- Software
Python
Permissions
File Scopes
Functions strictly in a passive, read-only buffer mode (file_system_write: false). Generates telemetry layout integrity reports completely offline with zero risk of corporate repository exposure or live code execution leakages.