diff --git a/CHANGES.rst b/CHANGES.rst
index 713c7f7ada40b84c3f7a3fd179e373af6afb48b4..04e9e6368077dd6b2abe004fc1aa31c48e4e2739 100644
--- a/CHANGES.rst
+++ b/CHANGES.rst
@@ -91,6 +91,9 @@ Baker
 Agnostic Baker
 --------------
 
+- Add ``run accuser`` command to replicate the behaviour of the accuser.
+  (MR :gl:`!17767`)
+
 - Enables ``advertises_level`` in baker logs by default, logs are prefixed by
   the logging level. It can be disabled by setting ``"log" : { advertises_level
   : false }`` in the client configuration. (MR :gl:`!17737`)
@@ -132,6 +135,13 @@ the README from ``src/bin_agnostic_baker``.
 Accuser
 -------
 
+Agnostic Accuser
+----------------
+
+- Add ``octez-accuser`` agnostic accuser binary. This behaves in a similar way
+  to the agnostic baker binary, automatically switching the underlying accuser
+  process at protocol migration. (MR :gl:`!17738`)
+
 Proxy Server
 ------------
 
diff --git a/src/bin_agnostic_accuser/README.md b/src/bin_agnostic_accuser/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..63a5d25845aad7479f4e7112f2a29d6e97958a01
--- /dev/null
+++ b/src/bin_agnostic_accuser/README.md
@@ -0,0 +1,34 @@
+# Agnostic Accuser
+
+## Overview
+
+Agnostic Accuser is a protocol-independent binary that dynamically selects the
+appropriate denunciation process based on the active protocol. It monitors the state of
+the blockchain and automatically switches to the correct process when a new
+protocol is encountered (for example, during migrations, or at startup).
+
+It is designed in a similar fashion to the **Agnostic Baker**, meaning that users
+will no longer need to use two accuser binaries for protocol migration, as this will
+be performed automatically by the agnostic accuser.
+
+## Usage
+
+In the same fashion as for the agnostic baker, to run the accuser we just replace
+the old `octez-accuser-<protocol>` binary with `octez-accuser` and keep the
+same arguments:
+
+```bash
+octez-accuser [OCTEZ-ACCUSER-COMMANDS]
+```
+
+Furthermore, for the `run` command of the accuser, the agnostic baker is equipped
+with a command to replicate the behaviour of the accuser binary:
+
+```bash
+octez-baker run accuser [OCTEZ-ACCUSER-COMMANDS]
+```
+
+## How it works
+
+The mechanism behind the agnostic accuser is the same as the one for the agnostic
+baker, so you can refer to that section for more in-depth information.
diff --git a/src/bin_agnostic_baker/README.md b/src/bin_agnostic_baker/README.md
index 184d8395a7a43cb5d927ace0e88a17ce2c1c4830..5c88519c6dbff010aa0f172ece5ae635e64ce28c 100644
--- a/src/bin_agnostic_baker/README.md
+++ b/src/bin_agnostic_baker/README.md
@@ -17,7 +17,7 @@ To run the agnostic baker, the command line syntax is similar to the one
 for the protocol-dependent baking binaries:
 
 ```bash
-./octez-baker [OCTEZ-BAKER-COMMANDS]
+octez-baker [OCTEZ-BAKER-COMMANDS]
 ```
 
 The `[OCTEZ-BAKER-COMMANDS]` list consists of all the arguments that can be used
@@ -25,7 +25,7 @@ for the specific protocol baking binary. To be more clear, if a user wants to us
 the agnostic baker to replace a baking command which would be
 
 ```bash
-./octez-baker-<protocol> [OCTEZ-BAKER-COMMANDS]
+octez-baker-<protocol> [OCTEZ-BAKER-COMMANDS]
 ```
 
 they can do this by using the same `[OCTEZ-BAKER-COMMANDS]` and let the agnostic