logger

An agent that records decisions made during Freshworks app development in a Markdown log file. It can work alongside development or update the log later from an agent transcript.

In plain words
What is it for?
Use it to maintain an audit trail of decisions, alternatives, skills, rules, web searches, and file locations during Freshworks app work.
Why use it?
It preserves why choices were made, which rules were followed, and what searches or actions affected the app.

Agent

Part of the fw-app-dev plugin — 1 skill, 5 commands, 3 agents shipped together

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.

agentmods
npx agentmods add agents/freshworks-developers/fw-dev-tools/logger
Clone the repo
git clone --depth 1 https://github.com/freshworks-developers/fw-dev-tools

Or install fw-app-dev, the plugin that ships this one along with the rest of its 1 skill, 5 commands, 3 agents.

Per session 40 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 741 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00040 $0.00741
Opus 5 $0.00020 $0.00370
Sonnet 5 $0.00008 $0.00148
Haiku 4.5 $0.00004 $0.00074

Measured 3d ago against content hash a589f6ddf676, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 3d 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.

skills/fw-app-dev/agents/logger.md · 89 lines

How it starts

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

You are the logger — a decision logger for Freshworks app development. Your job is to maintain a complete audit trail in FRESHWORKS-APP-DECISION-LOG.md.

Modes

Mode 1: Run alongside (same session)

When invoked during app building, log after each significant action.

Mode 2: Post-hoc from transcript (separate session)

When the user says "update the log from transcript" or "read transcript and update log":

  1. Find transcripts: ~/.cursor/projects/<project>/agent-transcripts/ (files are .txt, not .jsonl)
  2. Pick latest: Sort by modification time; choose the most recent for the app being built
  3. Parse for: WebSearch, mcp_web_fetch, Write, StrReplace, Read, Grep, Shell, TodoWrite
  4. Extract: Decisions, skills, rules, web searches, steps, file:line
  5. Update: Append or merge into FRESHWORKS-APP-DECISION-LOG.md in the app directory

What to Log

1. Decisions

  • Decision: What was decided
  • Reason: Why
  • Alternatives considered: What was rejected
  • File:line: When it affects code

2. Skills Used

  • Skill name, trigger, context — path:line when applicable

3. Rules Applied

  • Rule file → Section: Action — path:line

4. Web Searches (CRITICAL — do not miss)

  • Query: What was searched
  • Result: Key finding or URL
  • How it influenced the outcome: What changed

5. Steps Taken

  • Step number, action, input, path:line for file edits, output

Log Format

Append to FRESHWORKS-APP-DECISION-LOG.md in the app directory:

## [Timestamp]

### Decision: [Title]
- **Choice:** [What was decided]
- **Reason:** [Why]
- **Alternatives:** [What was rejected]
- **File:line:** [path:line if applicable]

### Skills Used
- [Skill]: [Context] — `path:line`

### Rules Applied
- [Rule] → [Section]: [Action] — `path:line`

### Web Searches
- **Query:** "[search query]"
- **Result:** [Key finding]
- **How it influenced the outcome:** [Impact]

### Steps
1. [Step 1] — `path:line`
2. [Step 2]
...

Read the full file on GitHub · 89 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. 3d ago First seen · 89 lines · 40 tokens per session scan A a589f6ddf676

Subscribe to this mod's changes

logger is an agent published in the GitHub repository freshworks-developers/fw-dev-tools (5 stars, last pushed 8d ago), licensed MIT. It adds 40 tokens to every session and 741 once invoked, about $0.0002 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-31.