frappe-logs

frappe-logs is a command for Claude Code from Venkateshvenki404224/frappe-apps-manager. It costs 13 tokens per session (2,808 once invoked), scanned A, original, MIT.

A command for reading and searching Frappe bench logs, which are records of requests, errors, background jobs, and scheduled tasks in a Frappe development environment.

In plain words
What is it for?
Use it to inspect web-server, worker, scheduler, error, site-specific, or combined logs, including recent entries or live output.
Why use it?
It brings related log files together and lets you narrow them by time, severity, or log type. This makes it easier to find the cause of failed requests, worker jobs, or scheduled tasks.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the frappe-apps-manager plugin — 16 skills, 16 commands, 3 hooks shipped together

Good fit Use it to inspect web-server, worker, scheduler, error, site-specific, or combined logs, including recent entries or live output.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/venkateshvenki404224/frappe-apps-manager/frappe-logs
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.

Clone the repo
git clone --depth 1 https://github.com/Venkateshvenki404224/frappe-apps-manager

Made for: Claude Code.

Or install frappe-apps-manager, the plugin that ships this one along with the rest of its 16 skills, 16 commands, 3 hooks.

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 frappe-logs

README.md
[![agentmods](https://agentmods.dev/badge/commands/venkateshvenki404224/frappe-apps-manager/frappe-logs/github.svg)](https://agentmods.dev/commands/venkateshvenki404224/frappe-apps-manager/frappe-logs)
Your own site
<a href="https://agentmods.dev/commands/venkateshvenki404224/frappe-apps-manager/frappe-logs"><img src="https://agentmods.dev/badge/commands/venkateshvenki404224/frappe-apps-manager/frappe-logs/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 frappe-logs

Your own site · 80×15
<a href="https://agentmods.dev/commands/venkateshvenki404224/frappe-apps-manager/frappe-logs"><img src="https://agentmods.dev/badge/commands/venkateshvenki404224/frappe-apps-manager/frappe-logs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,808 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.00013 $0.02808
Opus 5 $0.00006 $0.01404
Sonnet 5 $0.00003 $0.00562
Haiku 4.5 $0.00001 $0.00281

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

Security

Grade A, and why

frappe-logs 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 12d 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.

frappe-apps-manager/commands/frappe-logs.md · 473 lines

How it starts

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

Frappe Logs Command

View, filter, and analyze Frappe bench logs including web server, background workers, scheduler, and error logs.

Steps to Execute

1. Verify Bench Environment

  • Check if current directory is a valid Frappe bench
  • Look for logs/ directory
  • Verify log files exist

2. Determine Log Type to View

Ask user which logs to view:

A. Web Server Logs

  • logs/web.log - Werkzeug development server logs
  • logs/web.error.log - Web server error logs
  • Shows HTTP requests, responses, errors

B. Worker Logs

  • logs/worker.log - Background job worker logs
  • logs/worker.error.log - Worker errors
  • Shows async task execution

C. Scheduler Logs

  • logs/schedule.log - Scheduled task logs
  • Shows cron job execution

D. Site-specific Logs

  • sites/[site-name]/logs/ - Per-site logs
  • Request logs, error logs

E. All Logs

  • View combined logs from all sources

3. Log Viewing Options

Offer filtering and display options:

Time-based:

  • Last N lines (default: 50)
  • Last N minutes/hours
  • Specific time range
  • Real-time tail (follow mode)

Level-based:

  • ERROR only
  • WARNING and above
  • INFO and above
  • DEBUG (all logs)

Pattern-based:

  • Search for specific text/pattern
  • Filter by DocType name
  • Filter by user
  • Filter by IP address

4. Execute Log Viewing

Based on user choice, execute appropriate command:

View Recent Web Logs:

tail -n 50 logs/web.log

View Error Logs Only:

tail -n 100 logs/web.error.log

Follow Logs in Real-time:

tail -f logs/web.log

Search for Specific Pattern:

grep "pattern" logs/web.log | tail -n 50

View Logs with Timestamps:

tail -n 50 logs/web.log | grep -E '^\[.*\]'

Multiple Log Files:

tail -n 20 logs/web.log logs/worker.log logs/schedule.log

5. Format Log Output

Parse and display logs in readable format:

Standard Format:

[2025-12-15 14:30:45] ERROR: ValidationError in Document Customer
  File: frappe/model/document.py, Line: 234
  User: [email protected]
  Message: Email is required

Read the full file on GitHub · 473 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. 12d ago First seen · 473 lines · 13 tokens per session scan A da34f198b2d9

Subscribe to this mod's changes

frappe-logs is a command published in the GitHub repository Venkateshvenki404224/frappe-apps-manager (27 stars, last pushed 3mo ago), licensed MIT. It adds 13 tokens to every session and 2,808 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-08-30.