futile.logger

futile.logger is a skill for Claude Code, Codex from LeoLin990405/r-analytics-skill. It costs 25 tokens per session (864 once invoked), scanned A, original, MIT.

An R logging package with named, hierarchical loggers, message layouts, severity levels, and console or file outputs.

In plain words
What is it for?
Use it to record formatted application events, control thresholds for parent and child loggers, and write logs to the console or files.
Why use it?
It lets larger R applications separate messages by component and adjust how much detail each component produces.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to record formatted application events, control thresholds for parent and child loggers, and write logs to the console or files.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/leolin990405/r-analytics-skill/futile.logger
Install

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.

Any agent
npx skills add LeoLin990405/r-analytics-skill --skill futile.logger
Clone the repo
git clone --depth 1 https://github.com/LeoLin990405/r-analytics-skill

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for futile.logger

README.md
[![agentmods](https://agentmods.dev/badge/skills/leolin990405/r-analytics-skill/futile.logger/github.svg)](https://agentmods.dev/skills/leolin990405/r-analytics-skill/futile.logger)
Your own site
<a href="https://agentmods.dev/skills/leolin990405/r-analytics-skill/futile.logger"><img src="https://agentmods.dev/badge/skills/leolin990405/r-analytics-skill/futile.logger/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.

agentmods 80×15 button for futile.logger

Your own site · 80×15
<a href="https://agentmods.dev/skills/leolin990405/r-analytics-skill/futile.logger"><img src="https://agentmods.dev/badge/skills/leolin990405/r-analytics-skill/futile.logger.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 864 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00025 $0.00864
Opus 5 $0.00013 $0.00432
Sonnet 5 $0.00005 $0.00173
Haiku 4.5 $0.00003 $0.00086

Measured 8d ago against content hash 1e9a67ecce12, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

futile.logger 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 8d 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.

sub-skills/r-logging/futile.logger/SKILL.md · 172 lines

How it starts

The opening of the file, as written. The whole thing — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.

futile.logger

Log4j-style logging for R.

Basic Usage

library(futile.logger)

# Log messages
flog.trace("Trace message")
flog.debug("Debug message")
flog.info("Info message")
flog.warn("Warning message")
flog.error("Error message")
flog.fatal("Fatal message")

Formatted Messages

# Printf-style formatting
flog.info("Processing file: %s", filename)
flog.info("Completed %d of %d items", current, total)
flog.info("Value: %.2f", value)

# Multiple arguments
flog.info("User %s performed action %s at %s", user, action, time)

Log Levels

# Set threshold
flog.threshold(INFO)   # Show INFO and above
flog.threshold(DEBUG)  # Show DEBUG and above
flog.threshold(WARN)   # Show WARN and above

# Get current threshold
flog.threshold()

# Log level constants
TRACE, DEBUG, INFO, WARN, ERROR, FATAL

Named Loggers

# Create named logger
flog.threshold(DEBUG, name = "myapp")
flog.info("Message", name = "myapp")

# Hierarchical loggers
flog.threshold(INFO, name = "myapp")
flog.threshold(DEBUG, name = "myapp.database")

# Child inherits from parent unless overridden
flog.info("DB query", name = "myapp.database")

Appenders

# Console (default)
flog.appender(appender.console())

# File
flog.appender(appender.file("app.log"))

# Tee (console and file)
flog.appender(appender.tee("app.log"))

# Multiple appenders
flog.appender(appender.tee("app.log"), name = "myapp")

# Custom appender
my_appender <- function(line) {
  # Custom logic
  cat(line, "\n")
}
flog.appender(my_appender)

Layouts

# Default layout
flog.layout(layout.simple)

# With timestamp
flog.layout(layout.format('[~t] [~l] ~m'))

# Custom format
# ~l = level
# ~t = timestamp
# ~n = namespace
# ~f = calling function
# ~m = message

flog.layout(layout.format('[~t] [~l] [~n] ~m'))

# JSON layout
flog.layout(layout.json)

# Tracing layout (includes function name)
flog.layout(layout.tracing)

Conditional Logging

# Check if level is enabled
if (flog.logger()$threshold <= DEBUG) {
  # Expensive debug computation
  flog.debug("Expensive: %s", expensive_computation())
}

Read the full file on GitHub · 172 lines

Changes

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.

  1. 8d ago First seen · 172 lines · 25 tokens per session scan A 1e9a67ecce12

Subscribe to this mod's changes

futile.logger is a skill published in the GitHub repository LeoLin990405/r-analytics-skill (5 stars, last pushed 6mo ago), licensed MIT. It adds 25 tokens to every session and 864 once invoked, about $0.0001 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-09-03.

Related

Other skills, from other repositories

alibaba-observability-incident-responder

Respond to Alibaba Cloud incidents using CloudMonitor alarms, SLS log analytics, ARMS APM distributed tracing, and alert governance for ECS, RDS, ACK, and network services.

VincentChuWaiChow/vanguard-frontier-agentic · 47 tokens

azure-resource-health-incident-triage

Use this skill for Azure Resource Health, Service Health, activity-log alert, and first-pass incident triage when the question is whether Azure platform health is part of the problem.

VincentChuWaiChow/vanguard-frontier-agentic · 0 tokens

aws-observability-incident-responder

Investigate broad AWS incidents and observability gaps using CloudWatch metrics, logs, alarms, traces, EventBridge events, service health, runbooks, timelines, blast radius, root-cause discipline, and post-incident actions. Prefer RDS/Aurora investigator for database-specific performance incidents.

VincentChuWaiChow/vanguard-frontier-agentic · 68 tokens

aws-rds-aurora-performance-investigator

Investigate Amazon RDS and Aurora-specific incidents involving latency, connection exhaustion, slow queries, lock waits, storage pressure, CPU/I/O saturation, replica lag, failover behavior, Performance Insights, and database capacity. Prefer this for database performance; prefer broad observability responder for…

VincentChuWaiChow/vanguard-frontier-agentic · 70 tokens

azure-cosmosdb-performance-investigator

Use this skill for Azure Cosmos DB performance investigation, especially RU spikes, query latency, throttling, hot partitions, indexing inefficiency, partition-skew analysis, request-charge profiling, diagnostic-log review, and evidence-driven remediation planning.

VincentChuWaiChow/vanguard-frontier-agentic · 0 tokens

azure-observability-investigator

Use this skill for Azure Monitor, Log Analytics, Application Insights, alerting, KQL triage, telemetry-gap analysis, workbooks, or operator-grade incident and posture investigations.

VincentChuWaiChow/vanguard-frontier-agentic · 0 tokens