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 lingxling/awesome-skills-cn --skill 360-feedback-systemgit clone --depth 1 https://github.com/lingxling/awesome-skills-cnWrote 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/lingxling/awesome-skills-cn/360-feedback-system)<a href="https://agentmods.dev/skills/lingxling/awesome-skills-cn/360-feedback-system"><img src="https://agentmods.dev/badge/skills/lingxling/awesome-skills-cn/360-feedback-system/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/lingxling/awesome-skills-cn/360-feedback-system"><img src="https://agentmods.dev/badge/skills/lingxling/awesome-skills-cn/360-feedback-system.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.00045 | $0.05011 |
| Opus 5.5 | $0.00018 | $0.02004 |
| Sonnet 5.5 | $0.00009 | $0.01002 |
| Haiku 4.5 | $0.00005 | $0.00501 |
Grade A, and why
360-feedback-system 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 8d 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.
This is a copy
100% identical to 360-feedback-system — 17 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 482 lines — stays where its author put it; the contents beside it link to each section on GitHub.
360° Feedback System
What it is: Records one feedback response per row, with the field list built only from what the user confirms.
Overview
Works out the smallest useful 360° feedback setup for the business in front of it, then builds it only when asked. The default output is a short recommendation, not a spreadsheet. CSV, SQL DDL, JSON Schema and the Notion mapping are derived from the one Field Reference below, so they cannot drift apart.
Three conceptual models are kept separate, because merging them is what forces fields to be invented:
- Response - one row per feedback response. The only model with a table in this skill.
- Scoring Configuration - scale, weights, missing and not-applicable handling, rounding. Configuration, never a column on the response row.
- Questions - the question set and its version, held only when questions change between cycles. A question ID is a column on Response only once that requirement is confirmed.
Artifacts are empty templates by default. The single illustrative row is a shape placeholder
carrying Example / -EXAMPLE- values, never business data.
Layer: Layer 4: Manage. Fits: Growth stage. Table code: n/a.
When to Use This Skill
- 360 feedback
- feedback system
- peer review tool
- 360 degree feedback tracker
Also use it when the user says "holistic feedback", or describes the same process happening in a spreadsheet, a document or someone's inbox.
Not for payroll, tax, legal, or employment-decision work. This skill does not automate those.
How It Works
Follow the shared execution contract. The module-specific rules below define only domain fields, decisions, calculations, and safety constraints.
The rules below stand on their own. If the shared execution contract at
../../references/execution-contract.md is unavailable, follow this file directly; a missing
reference never blocks basic execution.
Step 1 - Identify intent
Read the request and pick one intent before asking anything. This is the canonical set, used here and in the context block with the same spelling:
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.
- 8d ago First seen · 482 lines · 45 tokens per session scan A 7ec858bd99cd
360-feedback-system is a skill published in the GitHub repository lingxling/awesome-skills-cn (307 stars, last pushed 8d ago), licensed MIT. It adds 45 tokens to every session and 5,011 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to 360-feedback-system, differing in 17 lines, and is treated as a copy.
Other skills, from other repositories
360-feedback-system
360 feedback register: reviewer, subject, review cycle, visibility, due date and score, as CSV, SQL, JSON Schema or Notion on request. Use for 360 reviews or peer feedback cycles.
alumni-re-hire-tracker
Alumni and re-hire register: former role, last working day, re-hire eligibility, current employer and re-engagement date, as CSV, SQL, JSON Schema or Notion on request. Use for alumni outreach.
announcement-board
Announcement board: author, category, department, priority, audience, publish and expiry dates, status and acknowledgements, as CSV, SQL, JSON Schema or Notion on request. Use for internal notices.
360-feedback-system
360 feedback register: reviewer, subject, review cycle, visibility, due date and score, as CSV, SQL, JSON Schema or Notion on request. Use for 360 reviews or peer feedback cycles.
admin-access-register
Admin account register: system, main and backup admin, seats, plan, 2FA, shared logins and access-review dates, as CSV, SQL, JSON Schema or Notion on request. Use for access reviews.
access-matrix
Access matrix of role-by-module permissions, with per-role scope, confidentiality level and SME tier, as CSV, SQL, JSON Schema or Notion on request. Use for access reviews.