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 ulises-jeremias/agent-toolkit --skill project-assessment-evidencegit clone --depth 1 https://github.com/ulises-jeremias/agent-toolkitWrote 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/ulises-jeremias/agent-toolkit/project-assessment-evidence)<a href="https://agentmods.dev/skills/ulises-jeremias/agent-toolkit/project-assessment-evidence"><img src="https://agentmods.dev/badge/skills/ulises-jeremias/agent-toolkit/project-assessment-evidence/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/ulises-jeremias/agent-toolkit/project-assessment-evidence"><img src="https://agentmods.dev/badge/skills/ulises-jeremias/agent-toolkit/project-assessment-evidence.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.00044 | $0.00787 |
| Opus 5.5 | $0.00018 | $0.00315 |
| Sonnet 5.5 | $0.00009 | $0.00157 |
| Haiku 4.5 | $0.00004 | $0.00079 |
Grade A, and why
project-assessment-evidence 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Assessment Evidence (WHAT)
Use this skill before scoring a project assessment. It turns scattered project knowledge into a structured evidence map.
This skill is intentionally interactive. Evidence can be outside ClickUp and outside the repository. Ask for source locations instead of assuming where they live.
Default behavior
- Ask the user for the systems of record and evidence locations.
- Collect source links, paths, owners, dates, and freshness for each evidence item.
- Mark evidence quality: Direct, Indirect, Interview-only, Stale, Missing, or Not applicable.
- Record confidence for each evidence item: High, Medium, Low, or Not assessed.
- Do not score indicators. Return the evidence map to
project-assessment,technical-unit-assessment, ormanagement-unit-assessment.
Evidence intake questions
Ask only the questions relevant to the assessment scope, but cover each required source class before scoring.
Scope and systems
- What project, product, platform, squad, or delivery scope is being assessed?
- What period should evidence cover?
- What are the official systems of record?
- Which sources should be considered authoritative when sources conflict?
Delivery and management evidence
- Where is the project board or backlog?
- Where are epics, stories, tasks, bugs, incidents, and subtasks tracked?
- Where are sprint plans, delivery reports, retrospectives, risks, and OIRs?
- Where are PRDs, TRDs, ADRs, decisions, agreements, and meeting minutes stored?
- Where can stakeholder feedback, client satisfaction signals, and team health signals be found?
- Who should validate subjective management indicators?
Technical evidence
- Where are the repositories and deployment manifests?
- Where are architecture diagrams, API docs, runbooks, and operations docs?
- Where are CI/CD pipelines, deployment history, and release notes?
- Where are test reports, coverage data, quality gates, and static analysis outputs?
- Where are observability dashboards, alerts, logs, incident records, and postmortems?
- Where are security, compliance, access control, secrets management, and dependency signals?
- For data systems, where are lineage, data quality checks, orchestration, schemas, business rules, and consumption docs?
- For UI/UX, where are design files, UX research, accessibility reports, performance reports, screenshots, recordings, or product analytics?
What ships with it
2 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.
- 1mo ago First seen · 89 lines · 44 tokens per session scan A f6720f1026d5
project-assessment-evidence is a skill published in the GitHub repository ulises-jeremias/agent-toolkit (19 stars, last pushed yesterday), licensed MIT. It adds 44 tokens to every session and 787 once invoked, about $0.0002 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-04.
Other skills, from other repositories
github-navigator
GitHub operations via gh CLI. CRITICAL: Use instead of WebFetch for any github.com URL or GitHub repo path like owner/repo. Use when the user asks to inspect repositories, files, issues, pull requests, releases, Actions runs, or repository structure. Use when the user says 'show README', 'list issues', 'check PR'…
create-jira-item
Create Jira issues (stories, epics, initiatives) with custom field introspection to fill org-specific fields correctly. Use when the user asks to create a Jira ticket, story, epic, initiative, or task.
implement-plan
Use when the user wants to execute an approved implementation plan and says any of "do it" (with a plan in scope), "lets do it" / "let's do it", "confirmed" (as approval to proceed on a plan), "implement the plan", "implement this", "execute the plan", "start implementing", "work through the plan", "implement the next…
breaking-down-work
Decomposes a goal, feature, epic, or deliverable into a structured task tree (tasks, subtasks, checklists) with dependencies in Astravue. Use when the user wants to break down, decompose, or plan out work, turn an epic or feature into tasks, "split this into tasks", scope a deliverable, or build a work breakdown…
capturing-meeting-actions
Extracts action items from meeting notes, transcripts, or a brain dump and creates them as owned, dated tasks in Astravue. Use when the user pastes meeting notes or a transcript, asks to turn notes or standup discussion into tasks, capture action items, or "make tasks out of this".
mapping-dependencies
Maps task dependencies in an Astravue project, finds the critical path and blocked work, and detects circular dependencies before any rescheduling. Use when the user asks about dependencies, blockers, what's blocking what, the critical path, or wants to understand or fix the sequencing of a project.