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.
npx skills add topprismdata/agent-nurture-framework --skill 03-bug-fixgit clone --depth 1 https://github.com/topprismdata/agent-nurture-frameworkWrote 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.
[](https://agentmods.dev/skills/topprismdata/agent-nurture-framework/03-bug-fix)<a href="https://agentmods.dev/skills/topprismdata/agent-nurture-framework/03-bug-fix"><img src="https://agentmods.dev/badge/skills/topprismdata/agent-nurture-framework/03-bug-fix/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.
<a href="https://agentmods.dev/skills/topprismdata/agent-nurture-framework/03-bug-fix"><img src="https://agentmods.dev/badge/skills/topprismdata/agent-nurture-framework/03-bug-fix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00153 | $0.01759 |
| Opus 5.5 | $0.00061 | $0.00704 |
| Sonnet 5.5 | $0.00031 | $0.00352 |
| Haiku 4.5 | $0.00015 | $0.00176 |
Grade A, and why
python-output-buffering-background-scripts 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Python Output Buffering Trap for Background Scripts
Problem
When a Python script is run in the background with output redirected to a file,
the log file may remain empty for hours even though the process is actively
running and producing output. This creates a misleading situation where the
process appears to be running correctly (it shows up in ps, consumes CPU and
memory) but produces no visible output. Developers waste time investigating
file permissions, path issues, or logging library configuration before
discovering the real cause: Python's output buffering behavior.
Context / Trigger Conditions
This skill should be triggered when:
- A log file or output file from a Python script is empty or incomplete, but
the process is confirmed to be running (
ps aux | grep script_nameshows an active process) - Running a Python script with
nohup python script.py > output.log 2>&1 &or similar background execution - Using systemd, supervisord, or cron to run Python scripts and logs are delayed
- A Python subprocess's stdout/stderr is not appearing in the parent process's logs in real time
- Output appears in the log file only after the process terminates or after a very long delay
The key diagnostic clue: the process is running but the log file is empty or significantly behind real time.
Solution
Root Cause
Python uses different buffering strategies depending on where stdout is connected:
- Connected to a terminal (TTY): Line buffering. Output is flushed after every newline character. This is the normal interactive behavior.
- Connected to a file or pipe (not a TTY): Fully buffered. Output is accumulated in a buffer (typically 4KB or 8KB) and only written when the buffer fills. For scripts that produce output infrequently (e.g., one line per minute during a long computation), the buffer may take hours to fill.
When you run python script.py > output.log 2>&1 &, stdout is connected to a
file, not a terminal. Python switches to fully buffered mode, and output is
delayed until the buffer fills.
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.
- 2d ago First seen · 218 lines · 153 tokens per session scan A cfdede9515c2
python-output-buffering-background-scripts is a skill published in the GitHub repository topprismdata/agent-nurture-framework (3 stars, last pushed 3d ago), licensed MIT. It adds 153 tokens to every session and 1,759 once invoked, about $0.0006 per session on Opus 5.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-10-14.
Other skills, from other repositories
prismer-python-debugpy
Debug Python: pdb REPL + debugpy remote (DAP).
python-run
Run and debug Python scripts in the project. Use when the user says "run python", "execute this script", "debug this py file", or wants to run/modify a .py file. Handles dependency checks, linting, execution, and error analysis.
python-debugpy
Debug Python: pdb REPL + debugpy remote (DAP).
python-code-quality
Code quality checks, linting, formatting, and type checking commands for the Agent Framework Python codebase. Use this when running checks, fixing lint errors, or troubleshooting CI failures.
plugin-architecture-patterns
Design, implement, or diagnose Xberg plugin traits, typed registries, priority collisions, lifecycle, native extractors, and Alef-generated Python plugin bridges. Load for plugin-system work, not ordinary extractor parsing.
test-corpus
The testdocuments submodule is a bucket-fetched fixture corpus that is not committed. This skill covers readtestfixture, missing fixtures, valid A/B controls, and submodule push order. Load before running Rust tests on a fresh clone, setting up an A/B control, adding a fixture-backed test, or diagnosing…