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 agentmods add skills/bartoszarendt/agenticloop/github-attributionnpx skills add bartoszarendt/agenticloop --skill github-attributiongit clone --depth 1 https://github.com/bartoszarendt/agenticloopWhat 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 | $0.00066 | $0.01189 |
| Opus 5 | $0.00033 | $0.00594 |
| Sonnet 5 | $0.00013 | $0.00238 |
| Haiku 4.5 | $0.00007 | $0.00119 |
Grade A, and why
github-attribution 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub attribution
This skill applies only when task_backend: github is set. Files-backed
projects do not post GitHub bodies or comments and do not use these trailers; see
agenticloop/backends/files.md.
When multiple agent roles share one GitHub token, GitHub's author field cannot identify which role wrote a comment. Agentic Loop uses a cooperative text trailer for role attribution.
This is not cryptographic. Treat missing or malformed attribution as unknown.
Body trailer
End every agent-authored issue, pull request, or comment body with one final line:
[[agent: orchestrator]]
[[agent: maintainer]]
[[agent: engineer]]
Use exactly one actual authoring role. Put the trailer after a blank line at the
end of the body. The accepted forms are [[agent: engineer]],
[[agent: maintainer]], and [[agent: orchestrator]].
Commit trailer
End every agent-authored commit message with:
Task: T-001
Agent: engineer
Use the linked issue's non-empty frontmatter task_id when it exists. For a
legacy issue without task_id, use its number instead, for example:
Task: #42
Agent: engineer
The body role and Agent: value must agree exactly. The Agent: value must be
the exact lowercase canonical roleId; a capitalized spelling such as
Agent: Engineer is rejected. The repair shape is always one final body trailer
[[agent: <role>]] and one final commit trailer pair
Task: <resolved task id> / Agent: <role>.
Prospective commit flow
Do not hand-author the message. task commit-message writes it, with the
canonical trailer block already in place and the role derived from the commit
class:
npx agenticloop task commit-message <task-id> --class <commit-class> --subject <text> --output .agenticloop/tmp/<task>-commit-message.txt
npx agenticloop commit-attribution check --task <task-id> --message-file .agenticloop/tmp/<task>-commit-message.txt
git commit -F .agenticloop/tmp/<task>-commit-message.txt
npx agenticloop commit-attribution check --task <task-id>
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 · 134 lines · 66 tokens per session scan A 49c0deba0630
github-attribution is a skill published in the GitHub repository bartoszarendt/agenticloop (2 stars, last pushed 12d ago), licensed MIT. It adds 66 tokens to every session and 1,189 once invoked, about $0.0003 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-31.
Other skills, from other repositories
consulting-analysis
Use this skill when the user requests to generate, create, or write professional research reports including but not limited to market analysis, consumer insights, brand analysis, financial analysis, industry research, competitive intelligence, investment due diligence, or any consulting-grade analytical report. This…
skill-creator
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
ppt-generation
Use this skill when the user requests to generate, create, or make presentations (PPT/PPTX). Creates visually rich slides by generating images for each slide and composing them into a PowerPoint file.
deerflow-maintainer-orchestrator
Use when a DeerFlow maintainer needs comment-only GitHub issue or PR handling: resolve issue/PR scopes with gh, analyze issues, post or draft issue comments, perform PR review comments, review PR or issue batches, compare competing PRs that target the same issue, give fix strategy, risk classification, and validation…
systematic-literature-review
Use this skill when the user wants a systematic literature review, survey, or synthesis across multiple academic papers on a topic. Also covers annotated bibliographies and cross-paper comparisons. Searches arXiv and outputs reports in APA, IEEE, or BibTeX format. Not for single-paper tasks — use academic-paper-review…
code-documentation
Use this skill when the user requests to generate, create, or improve documentation for code, APIs, libraries, repositories, or software projects. Supports README generation, API reference documentation, inline code comments, architecture documentation, changelog generation, and developer guides. Trigger on requests…