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 Firstp1ck/pi-coding-agent-forge --skill quickshell-localgit clone --depth 1 https://github.com/Firstp1ck/pi-coding-agent-forgeWrote 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/firstp1ck/pi-coding-agent-forge/quickshell-local)<a href="https://agentmods.dev/skills/firstp1ck/pi-coding-agent-forge/quickshell-local"><img src="https://agentmods.dev/badge/skills/firstp1ck/pi-coding-agent-forge/quickshell-local/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/firstp1ck/pi-coding-agent-forge/quickshell-local"><img src="https://agentmods.dev/badge/skills/firstp1ck/pi-coding-agent-forge/quickshell-local.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.00080 | $0.01611 |
| Opus 5.5 | $0.00032 | $0.00644 |
| Sonnet 5.5 | $0.00016 | $0.00322 |
| Haiku 4.5 | $0.00008 | $0.00161 |
Grade A, and why
quickshell-local 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 1mo 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quickshell local documentation
Use offline official Quickshell and Qt documentation to build source-backed components. The collection contains tutorials, the published Quickshell type reference and core Qt QML/Quick UI references. Do not confuse a search hit with a complete contract or assume the newest docs match installed libraries.
Setup and versions
- Setup or refresh:
/quickshell-wiki-local-setup. - Status:
/quickshell-wiki-status. - Health check:
/quickshell-wiki-smoke-testorquickshell_wiki_smoke_test({}). - Rollback:
/quickshell-wiki-local-setup --rollback. - Base path:
~/.quickshell-docs, configurable withQUICKSHELL_DOCS_PATH. - Full snapshots:
<base>.offline. The legacy clone remains untouched. - Selection: newest published stable Quickshell docs by default; an explicit
--versionorQUICKSHELL_DOCS_VERSIONcan pin a published version.
Setup discovers releases from the official website, not the source repository's default metadata. The repository previously listed v0.3.0 while the site already published v0.3.1. Never infer publication availability from that old file. Development master is usable only when actually published.
Always inspect docsVersion, sourceVersion, source, mode and coverage. Qt uses its own current Qt 6 documentation channel. Compare with quickshell --version and read-only installed Qt evidence before recommending newly introduced APIs. Installed .qmltypes under /usr/lib/qt6/qml/Quickshell/ can verify the local API on Linux, but they do not replace behavioral documentation.
If mode is legacy-guides, full API coverage has not been set up. Explain the setup requirement rather than claiming comprehensive evidence. If setup fails, preserve the reported missing source or version; do not silently substitute another release. Never install or refresh docs automatically without authorization.
Required retrieval workflow
- Search with
quickshell_wiki_search({ query, source, limit: 5 }). Use distinctive type/member names. The optionalsourceisquickshell-guide,quickshell-apiorqt; omit it for cross-source discovery. - Select a returned path or qualified type slug. Use
quickshell_wiki_sections({ page, maxSections: 40 }); increase the heading limit if the relevant member is omitted. - Extract an exact heading or original member anchor with
quickshell_wiki_extract({ page, section, maxChars: 6000, maxSections: 3 }). - Inspect the full relevant warning and prerequisites. For properties, also check required tracker/owner objects, read-only flags, nullability, ranges and related types. For functions/signals, check arguments, return types and lifecycle behavior.
- Check
matchedSections,omittedSectionCountandtruncated. A missing match returns empty text. Query extraction is useful for exploration, but exact member extraction is preferred for final evidence. - Follow
quickshell_wiki_relatedfor cross-source references. It resolves downloaded Quickshell/Qt URLs to local paths and reports missing eligible references. Read whole pages only when broad context is necessary. - Cite the returned local path and heading. Include the upstream
sourceUrland source version when useful, especially when Qt and Quickshell releases differ. - Verify the implementation separately with authorized lint/runtime checks. Documentation retrieval is not proof that a component works.
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.
- 1mo ago First seen · 85 lines · 80 tokens per session scan A 71d94542e9fd
quickshell-local is a skill published in the GitHub repository Firstp1ck/pi-coding-agent-forge (90 stars, last pushed yesterday), licensed MIT. It adds 80 tokens to every session and 1,611 once invoked, about $0.0003 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-09-13.
Other skills, from other repositories
nifra-web
Use when building the full-stack side of a Nifra app - file routes, layouts, loaders and actions, forms, server functions, streaming SSR, islands, SSG and ISR, the query cache, and the React, Vue, Solid, Svelte, or Preact render adapters. Covers the client/server boundary rules and the hydration errors that boundary…
convex-component-authoring
How to create, structure, and publish self-contained Convex components with proper isolation, exports, and dependency management.
npm-docs
Use this skill whenever the user asks about npm, package management, publishing packages, semantic versioning, npm CLI commands, or Node.js dependencies. Covers npm 12.x including the registry, scopes, organizations, security (audit, provenance, 2FA), CI/CD integration, workspaces, scripts, .npmrc configuration, and…
astro-integrations
Use when adding React, Vue, Svelte, Solid, Preact, or another UI framework to an Astro project via @astrojs/ integrations.
convex-component-authoring
How to create, structure, and publish self-contained Convex components with proper isolation, exports, and dependency management.
dependency-manager
Manage project dependencies — update packages, audit vulnerabilities, resolve conflicts, and keep dependencies healthy. Use when updating packages, fixing vulnerability alerts, or resolving dependency issues.