agentleFS
Wsh7AshWsh7Ash/skillmcp/skills/audit-log-of-tool-calls/SKILL.md

audit-log-of-tool-calls

Skill0 starsChanged 18 days agoMITView on GitHub

Log every call with arguments and outcome so an agent's actions can be reconstructed. Use when the server can change state or reach anything outside its own directory

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Verify a session can be reconstructed from the log alone

    line 25
  2. Distinctive:

    no credential value appears in any log line

    line 63

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Audit Log of Tool Calls

Log every call with arguments and outcome so an agent's actions can be reconstructed

Use when: the server can change state or reach anything outside its own directory

Avoid when: the server is read-only over public content and no audit is required

Procedure

  1. Decide the log destination: stderr, a file or both, never stdout
  2. Log timestamp, tool name, argument names and outcome
  3. Redact argument values that are credentials
  4. Log the failure reason for refused and errored calls
  5. Rotate or cap the log so it cannot fill the disk
  6. Verify a session can be reconstructed from the log alone

Signals

  • each call appears exactly once in the log
  • argument values that are secrets are redacted
  • refusals and errors are logged with reasons
  • the log never appears on stdout

Patterns

1. Structured line

{"ts":...,"tool":"get_skill","args":["slug"],"ok":true}

2. Redaction

args values logged as [redacted] when the key matches token|key|secret

3. Log size cap

rotate at 10 MB, keep three files

Pitfalls

  • Logging whole argument objects including credentials
  • Writing the audit log to stdout and breaking the protocol
  • Logging failures without the reason, making the entry useless

Done when

  • a session can be reconstructed from the log
  • no credential value appears in any log line

References

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.