Borrowing it
Nothing to install: this file belongs to sussdorff/timing-cli. 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/sussdorff/timing-cli/main/.agents/skills/cognovis-forgejo/SKILL.mdgit clone --depth 1 https://github.com/sussdorff/timing-cliWrote 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/sussdorff/timing-cli/cognovis-forgejo)<a href="https://agentmods.dev/skills/sussdorff/timing-cli/cognovis-forgejo"><img src="https://agentmods.dev/badge/skills/sussdorff/timing-cli/cognovis-forgejo/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/sussdorff/timing-cli/cognovis-forgejo"><img src="https://agentmods.dev/badge/skills/sussdorff/timing-cli/cognovis-forgejo.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.00033 | $0.01251 |
| Opus 5.5 | $0.00013 | $0.00500 |
| Sonnet 5.5 | $0.00007 | $0.00250 |
| Haiku 4.5 | $0.00003 | $0.00125 |
Grade A, and why
cognovis-forgejo 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 24d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cognovis Forgejo
Inspect git.cognovis.de Actions with fgj. fj lists tasks, not runs or logs.
Default host
Without a configured default, fgj 0.5.0 falls back to codeberg.org outside a
primary git.cognovis.de checkout, including every linked worktree. It picks the host in
this order:
- the
--hostnameflag; FGJ_HOSTNAME;- the top-level
hostname:key in$HOME/.config/fgj/config.yaml, read from$HOMEeven whenXDG_CONFIG_HOMEis set; FGJ_HOST;- the origin host of the current checkout, detected only where
.gitis a directory (a primary checkout). It fails in every linked worktree, including T3 thread worktrees and~/code/.worktrees; a GitHub checkout detectsgithub.com; codeberg.org.
The top-level hostname: git.cognovis.de key is the harness-neutral default. Nothing
provisions it per host: cognovis/harness-cli#31 planned that, but no released
harness bootstrap step (harness/v2026.10.1) provisions it yet. Until the check below
passes, pass --hostname git.cognovis.de (and -R owner/repo) or set
FGJ_HOSTNAME=git.cognovis.de. fgj auth login rewrites the hosts file
($XDG_CONFIG_HOME/fgj/config.yaml when set, else $HOME/.config/fgj/config.yaml) with
only hosts:; it drops the key when that is the same file. Because the key and
FGJ_HOSTNAME outrank remote detection, pass --hostname explicitly in a Codeberg or
GitHub checkout.
Whenever FGJ_TOKEN is exported, FGJ_HOSTNAME or FGJ_HOST is mandatory. With
FGJ_TOKEN set, an unconfigured host does not fail: fgj sends that token to the
fallback host, codeberg.org.
Check, with FGJ_TOKEN unset: env -u FGJ_TOKEN fgj api /version run from a directory
outside any checkout, such as /tmp, returns the git.cognovis.de Forgejo version.
no configuration found for host codeberg.org means the default is missing.
Inputs
owner/repoongit.cognovis.de, or a checkout whoseoriginis that hostfgjauth for that host, orFORGEJO_TOKENfrom~/.config/cognovis/forgejo.env
What ships with it
3 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.
- 24d ago Changed · +34 lines cb61497c320b
- 1mo ago First seen · 58 lines · 33 tokens per session scan A b69020ead385
cognovis-forgejo is a skill published in the GitHub repository sussdorff/timing-cli (1 stars, last pushed 10d ago), licensed MIT. It adds 33 tokens to every session and 1,251 once invoked, about $0.0001 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-24.
Other skills, from other repositories
repair-github-ci
Fix failing GitHub CI / Actions checks via fixgithubprci and push to the existing PR head, or fix a branch's failing CI via a linked repair worktree.
mcore-create-issue
Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.
debug-task
Diagnose and fix moon tasks that are broken, misconfigured, or behaving unexpectedly. Use this skill when a moon task is failing, not running, skipped, hanging, producing stale or wrong output, cached when it shouldn't be, re-running every time, or missing outputs after a cache hit. Also covers pipeline hangs, tasks…
operating-github-ci-fixer
Use when the user asks OpenSRE to fix failing GitHub CI, GitHub Actions checks, failing pull request checks, a broken PR branch, or CI on a named branch such as main.
meta-long-running-build-watchdog
Watches a long-running command via tmux, lets sub-agent diagnose failures and propose a fix, and records the diagnosis to memory. Designed for overnight model fine-tunes, CI image builds, or repeated regression suites that may fail intermittently.
gh-fix-ci
Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use gh to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treat external providers (for example Buildkite) as out of scope and report only the details URL.