Borrowing it
Nothing to install: this file belongs to Fioooooooo/FylloCode. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Fioooooooo/FylloCode/main/.agents/skills/adapt-acp-events/SKILL.mdgit clone --depth 1 https://github.com/Fioooooooo/FylloCodeWrote 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/fioooooooo/fyllocode/adapt-acp-events)<a href="https://agentmods.dev/skills/fioooooooo/fyllocode/adapt-acp-events"><img src="https://agentmods.dev/badge/skills/fioooooooo/fyllocode/adapt-acp-events/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/fioooooooo/fyllocode/adapt-acp-events"><img src="https://agentmods.dev/badge/skills/fioooooooo/fyllocode/adapt-acp-events.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Memory Poisoning · line 81 Skill injects content designed to persist in agent memory or context across interactions. Persistent injection can alter agent behavior long after the initial interaction.Fix: Do not allow untrusted input to persist in agent memory or context. Validate all content before storing and implement memory isolation between sessions.
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.00095 | $0.02926 |
| Opus 5 | $0.00048 | $0.01463 |
| Sonnet 5 | $0.00019 | $0.00585 |
| Haiku 4.5 | $0.00010 | $0.00293 |
Grade A, and why
adapt-acp-events 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 9d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adapt ACP Events
Turn real ACP traces into the narrowest evidence-backed compatibility change while preserving FylloCode's stable internal event semantics.
Read Before Acting
- Read the repository
AGENTS.mdand inspectgit status --short. - Read these files in full before changing covered areas:
guidelines/Architecture.mdguidelines/MainProcess.mdguidelines/Testing.mdguidelines/QualityGates.mdopenspec/specs/acp-tool-event-fidelity/spec.md
- Read the current mapper, normalizers, adapter types and registry, relevant adapters,
SessionEvent,MessageAssembler, shared tool-call assembly, and their tests. Treat current source and specs as authoritative; do not rely on paths or field behavior remembered from an earlier run. - Read adaptation-decision-matrix.md in full.
Establish the Adaptation Boundary
State whether the request is:
- new integration: add evidence and the narrowest adapter support for an Agent not yet optimized; or
- existing integration optimization: reproduce and correct a known mapping or display mismatch.
Record the canonical agentId, display name, actual running version, version source, ACP SDK version, and underlying Agent version when a bridge or adapter is involved. Prefer a detected or command-reported version over a registry latest version. Use null with agentVersionSource: "unavailable" when the actual version cannot be established; never silently omit it or substitute latestVersion.
Do not execute an arbitrary custom Agent with --version. Use already available status, package, registry, or user-provided evidence. If version discovery would launch unknown code or mutate state, ask first.
Capture Real Evidence
Capture representative session/update sequences, not isolated screenshots or normalized output. Build a version-scoped tool inventory before sampling instead of assuming standardized tool names:
- Discover the complete tool set exposed by the target Agent/version from authoritative, non-mutating sources available for that Agent, such as its tool listing or help surface, registry/configuration, session capabilities, and prior raw traces. Include dynamically provided MCP, skill, mode-specific, and subagent tools when they are available.
- Preserve each exact raw tool name or identifier and the source that proved its availability before applying any semantic normalization. Do not collapse Agent-specific names into generic categories during evidence collection.
- Attempt at least one safe representative invocation for every discovered tool. Exercise conditional tools by entering their required mode or configuration when that is safe and already authorized.
- Keep a coverage ledger in the versioned analysis document with the discovered tool, exact raw name or identifier, observed raw title variants, inventory source, sampled scenarios, observed update shapes, semantic family candidate, coverage status, and any skip or blocked reason.
- Use read, search, edit, execute, fetch, MCP, and subagent only as fallback semantic coverage dimensions for finding inventory gaps, never as an allowlist or a substitute for the Agent's actual tool inventory.
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 153 lines · 95 tokens per session scan A 0de00aa37636
adapt-acp-events is a skill published in the GitHub repository Fioooooooo/FylloCode (29 stars, last pushed 3d ago), licensed MIT. It adds 95 tokens to every session and 2,926 once invoked, about $0.0005 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.
Other skills, from other repositories
qa-testing
Verify your work by actually operating the app or website you changed, instead of assuming it works. Strongly recommended whenever you build, modify, or debug a web app, website, or desktop GUI app. Drive real browsers with the agent-browser CLI and native desktop apps with the cua-driver CLI. These are installed on…
build-teaql-app
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…
ultra-adlc
End-to-end delivery orchestration for explicitly requested, very large software changes that must be completely implemented and independently proven. Use when the user invokes "ultra-adlc" or asks for an Ultra-ADLC-scale full delivery; do not use for ordinary features, small fixes, reviews, or ad hoc parallel work.
go-127
What changed in Go 1.27 (released August 2026) and how it changes the way Go is written in pi-go. Use this skill when writing or reviewing Go that could use a 1.27 feature, when bumping the go directive in go.mod, when a build or test behaves differently after a toolchain upgrade, or when code-guidelines-go points…
bubbletea-testing
Use this skill whenever writing tests for Bubble Tea (charmbracelet/bubbletea) TUI applications in Go. Triggers include any mention of testing Bubble Tea models, teatest, golden file testing for TUIs, testing tea.Cmd or tea.Msg, snapshot testing terminal output, or writing tests for any Go CLI/TUI that uses the Elm…
pi-loop-forensics
Diagnose pi-go agent loops and degenerate turns — "agent loop aborted", runaway thinking with no tool calls, repeated phrases. Discriminates genuine model repetition collapse from a race, a tool-parse failure, or a too-low guard, and A/B replays a seed session across providers.