sceptre-mcp-server: Instructions file for Kiro

.kiro/steering/logging.md

sceptre-mcp-server logging.md is an instructions file for Kiro from Sceptre/sceptre-mcp-server. It costs 206 tokens per session, scanned A, original, Apache-2.0.

A set of rules for writing application logs: messages that record what software is doing. It covers log levels, useful context, machine-readable fields, and protecting secrets and personal information.

In plain words
What is it for?
Use it to decide when to log routine activity, warnings, and failures; include identifiers for tracing requests; and remove passwords, tokens, and other sensitive data from logs.
Why use it?
It prevents production logs from becoming noisy, hard to search, or unsafe. It also replaces scattered print statements with consistent records for diagnosing problems.

Instructions file for Kiro

Written for Kiro: installed under .kiro/.

This is Sceptre/sceptre-mcp-server's own configuration. It tells Kiro how to work on sceptre-mcp-server itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything sceptre-mcp-server configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Sceptre/sceptre-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Sceptre/sceptre-mcp-server/main/.kiro/steering/logging.md
Clone the repo
git clone --depth 1 https://github.com/Sceptre/sceptre-mcp-server

Made for: Kiro.

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 sceptre-mcp-server logging.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/sceptre/sceptre-mcp-server/logging/github.svg)](https://agentmods.dev/instructions/sceptre/sceptre-mcp-server/logging)
Your own site
<a href="https://agentmods.dev/instructions/sceptre/sceptre-mcp-server/logging"><img src="https://agentmods.dev/badge/instructions/sceptre/sceptre-mcp-server/logging/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 sceptre-mcp-server logging.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/sceptre/sceptre-mcp-server/logging"><img src="https://agentmods.dev/badge/instructions/sceptre/sceptre-mcp-server/logging.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 206 This file is loaded in full into every session.
When invoked 206 The same file — it is already loaded in full.
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.00206 $0.00206
Opus 5 $0.00103 $0.00103
Sonnet 5 $0.00041 $0.00041
Haiku 4.5 $0.00021 $0.00021

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

Security

Grade A, and why

sceptre-mcp-server logging.md 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 4d 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.

.kiro/steering/logging.md · 26 lines

What it actually says

Logging

Levels

  • DEBUG — detailed diagnostic info, development only
  • INFO — routine operations, request handling, state changes
  • WARNING — unexpected but recoverable situations
  • ERROR — failures that need attention but don't crash the app
  • CRITICAL — system-level failures requiring immediate action

Conventions

  • Use the logging module, never print() in production code
  • Include context: who, what, why (user ID, operation, relevant IDs)
  • Use structured logging (key-value pairs) for machine-parseable output
  • Set appropriate log levels per environment (DEBUG in dev, INFO in prod)

Security

  • Never log secrets, passwords, tokens, or API keys
  • Sanitize PII before logging (mask emails, redact names)
  • Don't log full request/response bodies in production
  • Audit log output regularly for sensitive data leaks
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. 4d ago First seen · 26 lines · 206 tokens per session scan A fcc5c1302edd

Subscribe to this mod's changes

sceptre-mcp-server logging.md is an instructions file published in the GitHub repository Sceptre/sceptre-mcp-server (0 stars, last pushed 5d ago), licensed Apache-2.0. It adds 206 tokens to every session, about $0.0010 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-08.

Related

Other instructions, from other repositories

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,126 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,469 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens